Adding issue dependencies is defunct in 1.6.0

[tinxx]

• 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

[Akcaxup]

On PostgreSQL also

[MarkusAmshove]

Thie is a duplicate of #5389

[lunny]

@tinxx please confirm #5392 fix this.

[tinxx]

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.

[MarkusAmshove]

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.

[tinxx]

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:

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. 😕