Performance / User Experience for Issue Dependencies #5992

New Issue

GiteaMirror · 2025-11-02T06:42:07-06:00

GiteaMirror commented

2025-11-02 06:42:07 -06:00

Originally created by @lhinderberger on GitHub (Sep 13, 2020).

Gitea version (or commit ref): 1.12.4

Description

Hello everyone! 👋

First of all, thank you for providing a mechanism to define issue dependencies. I think this is a very useful way to help to maintain an overview.

Unfortunately there's a performance / user experience problem with the current state of this feature, of which I want to make you aware:

In larger instances, such as Codeberg, defining issue dependencies can be very slow. It takes about ten seconds until the list of issues for the current repository is shown when clicking into the "Add Dependency" box. Searching for issue titles takes a few seconds too. It's also not possible to add an issue dependency by referring to the issue ID similar to how it would be done in Markdown (which at least to me is the most natural way of referring to an issue). This makes the process of adding dependencies rather hard to use.

The original discussion can be found at https://codeberg.org/Codeberg/Community/issues/244

Thank you!

Originally created by @lhinderberger on GitHub (Sep 13, 2020). - Gitea version (or commit ref): 1.12.4 ## Description Hello everyone! 👋 First of all, thank you for providing a mechanism to define issue dependencies. I think this is a very useful way to help to maintain an overview. Unfortunately there's a performance / user experience problem with the current state of this feature, of which I want to make you aware: In larger instances, such as Codeberg, defining issue dependencies can be very slow. It takes about ten seconds until the list of issues for the current repository is shown when clicking into the "Add Dependency" box. Searching for issue titles takes a few seconds too. It's also not possible to add an issue dependency by referring to the issue ID similar to how it would be done in Markdown (which at least to me is the most natural way of referring to an issue). This makes the process of adding dependencies rather hard to use. The original discussion can be found at https://codeberg.org/Codeberg/Community/issues/244 Thank you!

GiteaMirror added the performance/speed type/bug labels 2025-11-02 06:42:07 -06:00

GiteaMirror closed this issue

2025-11-02 06:42:07 -06:00

GiteaMirror commented

2025-11-02 06:42:08 -06:00

@6543 commented on GitHub (Mar 11, 2021):

time curl 'https://try.gitea.io/api/v1/repos/issues/search?q=&priority_repo_id=14718&type=all&_=1615487205723' > /dev/zero
-> 0m54,040s

@6543 commented on GitHub (Mar 11, 2021): `time curl 'https://try.gitea.io/api/v1/repos/issues/search?q=&priority_repo_id=14718&type=all&_=1615487205723' > /dev/zero` -> 0m54,040s

GiteaMirror commented

2025-11-02 06:42:08 -06:00

@zeripath commented on GitHub (Mar 27, 2021):

OK the issue is that /api/v1/repos/issues/search is just seriously inefficient.

@zeripath commented on GitHub (Mar 27, 2021): OK the issue is that /api/v1/repos/issues/search is just seriously inefficient.

GiteaMirror commented

2025-11-02 06:42:08 -06:00

@zeripath commented on GitHub (Mar 29, 2021):

Looking at try.gitea.io it appears that the improvement from #15179 could actually be sufficient to close this issue! Although I would still argue that the API is still too non-performant.

@zeripath commented on GitHub (Mar 29, 2021): Looking at try.gitea.io it appears that the improvement from #15179 could actually be sufficient to close this issue! Although I would still argue that the API is still too non-performant.

GiteaMirror commented

2025-11-02 06:42:09 -06:00

@6543 commented on GitHub (Jul 13, 2021):

yes main reason for this issue is gone - we could close it, but I like to keep it open until next release just to have a hint wat areas we can still improve a lot ;)

@6543 commented on GitHub (Jul 13, 2021): yes main reason for this issue is gone - we could close it, but I like to keep it open until next release just to have a hint wat areas we can still improve a lot ;)

GiteaMirror commented

2025-11-02 06:42:09 -06:00

@lunny commented on GitHub (Nov 14, 2021):

I think we can close this now. And if there is still new performance problem. We can create a new one.

@lunny commented on GitHub (Nov 14, 2021): I think we can close this now. And if there is still new performance problem. We can create a new one.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#5992