Description
Description
Following #27722 I decided to create separate issue for adding dependencies.
I have an Organization with several repositories.
Repository 1 have Issue R1_I1 and R1_I2
Repository 2 have Issue R2_I1 and R2_I2
R1_I2 depends on R1_I1
R2_I2 depends on R2_I1
and
R2_I1 depends on R1_I1
R2_I2 depends on R1_I2
While adding in-repository dependencies it is okay, but when I try to add dependency for cross-repository issues, required issue is just not shown in dropdown.
When I want to add R1_I1 as dependency for R2_I1 filter says nothing found, but if I wand to add R1_I2 as dependency, it magically displays R2_I1 .
Using this trick I can add one dependency, but not the other.
Overall , in dependency dropdown some kind on random results are shown.
And I cannot reproduce this kind of problem on try.gitea.io
but on https://try.gitea.io/n.kobzarev/front_repo/issues/2 I'm unable to remove "back_issue_feature_1", and it is not readable for unknown reason.
Gitea Version
1.22.0+dev-249-ge75b89ea6
Can you reproduce the bug on the Gitea demo site?
Yes
Log Gist
No response
Screenshots
Git Version
No response
Operating System
No response
How are you running Gitea?
windows service
Database
SQLite