Codeberg/Community
54
325
Fork
You've already forked Community
12

improve issue dependency search #619

Closed
opened 2022年05月08日 19:52:50 +02:00 by gerhardbeck · 12 comments

Ich beginne gerade das erste Mal mit Abhängigkeiten bei Issues zu arbeiten und die Suche treibt mich etwas zur Verzweiflung.

  • es scheint nicht zu gehen, dass man nur mit # und Zahl sucht
  • bei der Suche mit Titel will sie anscheinend den korrekten Anfang des Issues
  • sinnvoll erschiene mir, wenn zuerst passende Issues aus der gleichen Repo bzw. Der gleichen Organisation erscheinen würden - das scheint nicht der Fall zu sein.
Ich beginne gerade das erste Mal mit Abhängigkeiten bei Issues zu arbeiten und die Suche treibt mich etwas zur Verzweiflung. - es scheint nicht zu gehen, dass man nur mit # und Zahl sucht - bei der Suche mit Titel will sie anscheinend den korrekten Anfang des Issues - sinnvoll erschiene mir, wenn zuerst passende Issues aus der gleichen Repo bzw. Der gleichen Organisation erscheinen würden - das scheint nicht der Fall zu sein.
Owner
Copy link

Codeberg is an international and global community. Please write in English here. Auto-translated:

I am just starting to work with dependencies on issues for the first time and the search is driving me a bit to despair.

  • it doesn't seem to work to search only with # and number
  • when searching with title it seems to want the correct beginning of the issue
  • it would make sense to me if matching issues from the same repo or the same organization would appear first - this does not seem to be the case.

I agree, the search is very suboptimal. We've been working on the performance recently, maybe this can be one of the next steps.

To the second point: No, it shouldn't need the start, but exact / full words, e.g. you can't find an issue with "blah v1.09.3" by searching for "1.09.3" or "v1.09", you must search "v1.09.3" exactly.

Codeberg is an international and global community. Please write in English here. Auto-translated: > I am just starting to work with dependencies on issues for the first time and the search is driving me a bit to despair. > - it doesn't seem to work to search only with # and number > - when searching with title it seems to want the correct beginning of the issue > - it would make sense to me if matching issues from the same repo or the same organization would appear first - this does not seem to be the case. --- I agree, the search is very suboptimal. We've been working on the performance recently, maybe this can be one of the next steps. To the second point: No, it shouldn't need the start, but exact / full words, e.g. you can't find an issue with "blah v1.09.3" by searching for "1.09.3" or "v1.09", you must search "v1.09.3" exactly.

Sorry, just forgot to write in English instead of German.

ok, I wasn't aware of the need of full words. I'd suggest partial search, too

Sorry, just forgot to write in English instead of German. ok, I wasn't aware of the need of full words. I'd suggest partial search, too
fnetX changed title from (削除) Abhänigkeitensuche verbessern (削除ここまで) to improve issue dependency search 2022年05月10日 18:02:09 +02:00

This is really confusing and weird. I had to come to this issue to make progress :-)

If performance is not easy to fix and takes some time, could a stop gap measure be to put a little [?]->popup button with a short explanation like

Use complete words to search. Expect it to be slow. See issue #619

just after the "Dependencies" text?

This is really confusing and weird. I had to come to this issue to make progress :-) If performance is not easy to fix and takes some time, could a stop gap measure be to put a little [?]->popup button with a short explanation like > Use complete words to search. Expect it to be slow. See issue https://codeberg.org/Codeberg/Community/issues/619 just after the "Dependencies" text?

This is still very confusing to use.

This is still very confusing to use.

It is not just confusing, it just doesn't work. I think it would be
better to disable it at this point.

It is not just confusing, it just doesn't work. I think it would be better to disable it at this point.

forgejo/forgejo#8003 will improve the situation.

forgejo/forgejo#8003 will improve the situation.

@Gusted wrote in #619 (comment):

forgejo/forgejo#8003 will improve the situation.

When will it be enabled on codeberg?

@Gusted wrote in https://codeberg.org/Codeberg/Community/issues/619#issuecomment-5678216: > forgejo/forgejo#8003 will improve the situation. When will it be enabled on codeberg?

When Forgejo v13 is deployed. We might backport it sooner.

When Forgejo v13 is deployed. We might backport it sooner.

Is inability to add dependencies by exact reference or url also fixed by that PR? I'm fine without search but would be nice to add deps when I already have the url/reference handy.

Screencast example

(Gnome screen recording doesn't show my cursor, unfortunately.)

Is inability to add dependencies by exact reference or url also fixed by that PR? I'm fine without search but would be nice to add deps when I already have the url/reference handy. <details><summary>Screencast example</summary> (Gnome screen recording doesn't show my cursor, unfortunately.) <video src="/attachments/e335c8b6-377f-4854-9f5f-842a7874d8dc" title="Screencast From 2025年09月13日 17-10-38" controls></video> </details>

Actually I think I can answer my own question using the next instance— it does not. I'll open a new issue.

Actually I think I can answer my own question using the next instance— it does not. I'll open a new issue.
Owner
Copy link

I agree that entering a reference should allow adding a dependency without the need to perform an actual search. Did you create an issue in Forgejo yet?

I agree that entering a reference should allow adding a dependency without the need to perform an actual search. Did you create an issue in Forgejo yet?
https://codeberg.org/forgejo/forgejo/issues/9296
Sign in to join this conversation.
No Branch/Tag specified
main
No results found.
Labels
Clear labels
accessibility

Reduces accessibility and is thus a "bug" for certain user groups on Codeberg.
bug

Something is not working the way it should. Does not concern outages.
bug
infrastructure

Errors evidently caused by infrastructure malfunctions or outages
Codeberg

This issue involves Codeberg's downstream modifications and settings and/or Codeberg's structures.
contributions welcome

Please join the discussion and consider contributing a PR!
docs

No bug, but an improvement to the docs or UI description will help
duplicate

This issue or pull request already exists
enhancement

New feature
infrastructure

Involves changes to the server setups, use `bug/infrastructure` for infrastructure-related user errors.
legal

An issue directly involving legal compliance
licence / ToS

involving questions about the ToS, especially licencing compliance
please chill
we are volunteers

Please consider editing your posts and remember that there is a human on the other side. We get that you are frustrated, but it's harder for us to help you this way.
public relations

Things related to Codeberg's external communication
question

More information is needed
question
user support

This issue contains a clearly stated problem. However, it is not clear whether we have to fix anything on Codeberg's end, but we're helping them fix it and/or find the cause.
s/Forgejo

Related to Forgejo. Please also check Forgejo's issue tracker.
s/Forgejo/migration

Migration related issues in Forgejo
s/Pages

Issues related to the Codeberg Pages feature
s/Weblate

Issue is related to the Weblate instance at https://translate.codeberg.org
s/Woodpecker

Woodpecker CI related issue
security

involves improvements to the sites security
service

Add a new service to the Codeberg ecosystem (instead of implementing into Gitea)
upstream

An open issue or pull request to an upstream repository to fix this issue (partially or completely) exists (i.e. Gitea, Forgejo, etc.)
wontfix

Codeberg's current set of contributors are not planning to spend time on delegating this issue.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
6 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Codeberg/Community#619
Reference in a new issue
Codeberg/Community
No description provided.
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?