github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-12 02:24:21 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Adding issue dependencies is defunct in 1.6.0 #2629

New Issue
Closed
opened 2025-11-02 04:42:47 -06:00 by GiteaMirror · 6 comments
GiteaMirror commented 2025-11-02 04:42:47 -06:00
Owner
Copy Link

Originally created by @tinxx on GitHub (Dec 6, 2018).

  • Gitea version (or commit ref):
  • Git version: 1.6.0
  • Operating system: Debian Buster
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:

Description

Can you confirm that adding dependencies is broken in Gitea version 1.6.0?

When trying to add a dependent issue to another issue I always get the result:

No results found.

I get the following message when I try adding a dependency by it's id (11 or #11).

Dependent issue does not exist.

Screenshots

screenshot from 2018-12-06 16-58-01
screenshot from 2018-12-06 16-58-10

Originally created by @tinxx on GitHub (Dec 6, 2018). - Gitea version (or commit ref): - Git version: 1.6.0 - Operating system: Debian Buster - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [x] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [ ] Not relevant - Log gist: ## Description Can you confirm that adding dependencies is broken in Gitea version 1.6.0? When trying to add a dependent issue to another issue I always get the result: > No results found. I get the following message when I try adding a dependency by it's id (`11` or `#11`). > Dependent issue does not exist. ## Screenshots ![screenshot from 2018-12-06 16-58-01](https://user-images.githubusercontent.com/13608545/49595634-b7cf2d80-f978-11e8-9d8a-18685fe63b97.png) ![screenshot from 2018-12-06 16-58-10](https://user-images.githubusercontent.com/13608545/49595638-b7cf2d80-f978-11e8-9b18-68a7862310fe.png)
GiteaMirror added the type/bugissue/duplicate labels 2025-11-02 04:42:47 -06:00
GiteaMirror commented 2025-11-02 04:42:48 -06:00
Author
Owner
Copy Link

@Akcaxup commented on GitHub (Dec 8, 2018):

On PostgreSQL also
2580 _cr

@Akcaxup commented on GitHub (Dec 8, 2018): On PostgreSQL also ![2580 _cr](https://user-images.githubusercontent.com/32159064/49686376-9a2ecf00-fb04-11e8-927e-3a9ff5483b12.png)
GiteaMirror commented 2025-11-02 04:42:48 -06:00
Author
Owner
Copy Link

@markusamshove commented on GitHub (Dec 8, 2018):

Thie is a duplicate of #5389

@markusamshove commented on GitHub (Dec 8, 2018): Thie is a duplicate of #5389
GiteaMirror commented 2025-11-02 04:42:48 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Dec 8, 2018):

@tinxx please confirm https://github.com/go-gitea/gitea/pull/5392 fix this.

@lunny commented on GitHub (Dec 8, 2018): @tinxx please confirm https://github.com/go-gitea/gitea/pull/5392 fix this.
GiteaMirror commented 2025-11-02 04:42:49 -06:00
Author
Owner
Copy Link

@tinxx commented on GitHub (Dec 8, 2018):

I can confirm that it is the same API error on my instance. I am not a Gitea developer though and cannot confirm if the patch solves the issue.

@tinxx commented on GitHub (Dec 8, 2018): I can confirm that it is the same API error on my instance. I am not a Gitea developer though and cannot confirm if the patch solves the issue.
GiteaMirror commented 2025-11-02 04:42:49 -06:00
Author
Owner
Copy Link

@markusamshove commented on GitHub (Dec 8, 2018):

My workaround (which should be able to confirm if it is the same issue), which I'm not sure if it is recommended, is to create a file called sidebar.tmpl in custom/templates/repo/issue/view_content with this content.

The workaround is in this line.

Note that it is not quite the same change as in the PR, because I didn't also want to change the JS file.
I've added a / at the start to emulate the change in JS and changed RepoLink to RepoRelPath

If you look at the diff in the PR it shows the leading / in JS and change to RepoRelPath in the template.

@markusamshove commented on GitHub (Dec 8, 2018): My workaround (which should be able to confirm if it is the same issue), which I'm not sure if it is recommended, is to create a file called `sidebar.tmpl` in `custom/templates/repo/issue/view_content` with this [content](https://gist.github.com/MarkusAmshove/f66652074b44e3c8d6bf7710f0d858f4). The workaround is in this [line](https://gist.github.com/MarkusAmshove/f66652074b44e3c8d6bf7710f0d858f4#file-sidebar-tmpl-L342). Note that it is not quite the same change as in the PR, because I didn't also want to change the JS file. I've added a `/` at the start to emulate the change in JS and changed `RepoLink` to `RepoRelPath` If you look at the [diff](https://github.com/go-gitea/gitea/pull/5392/files) in the PR it shows the leading `/` in JS and change to `RepoRelPath` in the template.
GiteaMirror commented 2025-11-02 04:42:49 -06:00
Author
Owner
Copy Link

@tinxx commented on GitHub (Dec 9, 2018):

I reviewed the differences between your version and 1.6.0 version and found that only the / was added (next to format changes).

Adding the slash really fixed the problem for me. There are, however, strange layout glitches:
screenshot from 2018-12-09 10-44-41

What's more, I tried adding #31 as dep for #32 but the menu only allowed me to add #32 itself: Whenever I type #31 into the dependencies filter / search field of ticket #32, it displays only #32. 😕

@tinxx commented on GitHub (Dec 9, 2018): I reviewed the differences between your version and [1.6.0 version](https://raw.githubusercontent.com/go-gitea/gitea/release/v1.6/templates/repo/issue/view_content/sidebar.tmpl) and found that only the `/` was added (next to format changes). Adding the slash really fixed the problem for me. There are, however, strange layout glitches: ![screenshot from 2018-12-09 10-44-41](https://user-images.githubusercontent.com/13608545/49695789-55587600-fba0-11e8-8ac6-b0243f74cc65.png) What's more, I tried adding `#31` as dep for `#32` but the menu only allowed me to add `#32` itself: Whenever I type `#31` into the dependencies filter / search field of ticket `#32`, it displays only `#32`. :confused:
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label issue/duplicate type/bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#2629
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?