Issue dependencies ui kind of broken

[Aragur]

• Gitea version (or commit ref): cc9fa06
• Git version: 2.18.0
• Operating system: Debian
• Database:
  • MySQL
• Can you reproduce the bug at https://try.gitea.io:
  • Yes: https://try.gitea.io/Aragur/Issue-Dependency_Issue/issues

Description

In the dependencies list it only lists the last 8 issues relative to that one. For example issue #12 can only see issues #11 to #3. Also manual mention (for example of #1) doesn’t work.
Thanks to @Morlinest we already know more details:
Current work around is to search the exact issue name to add another.
Direct mention of the issue id is not working (but this should a thing).

Screenshots

Try to select #1 on issue #12

[jonasfranz]

Ping @kolaente

[kolaente]

This is something which should be fixed directly in the issue search, as I'm only using that (via the api). The results are the same as when you search on {projecturl}/issues.

I agree the issue search is not very good implemented.

[kolaente]

I'd rather have the search return issues by their index instead of frankensteining this into the dependencies.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

[stevegt]

Just noticed that direct mention of the issue id is still not working as of 7d973ed.

[zeripath]

@stevegt could you give a quick example of what you mean. Preferably with a try.gitea.io link?

It might be best to open another issue since this one is closed.

[stevegt]

@zeripath A 'try' link won't help -- go to any issue you can edit and enter an issue number into the 'dependencies' field, either with or without a leading '#'. You'll see that you get an error response of 'Dependent issue does not exist.'

This issue was recently closed by stale bot due to lack of activity, not because it's been addressed. There has been no merge referencing it. Re-opening would be the normal thing to do, rather than fragment the conversation. I'll let it sit for a while to see if anyone with access re-opens. I may get to this with a fix myself at some point as well.