Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Global issues search #2434

Open
lunny opened this issue Aug 30, 2017 · 8 comments

Comments

4 participants
@lunny
Copy link
Member

commented Aug 30, 2017

Currently we have issues where you can find all your related issues. But when the issues are too much, maybe you want to search them.

@lunny lunny added the kind/feature label Aug 30, 2017

@lunny lunny added this to the 1.x.x milestone Aug 30, 2017

@kolaente

This comment has been minimized.

Copy link
Member

commented Sep 25, 2017

It probably is very inperformant, to go through every issue when you issue a search, so: should we cache? (And how?)

Caching would probably mean to put every issue in a redis/memstore with everything that belongs to it.

@stevegt

This comment has been minimized.

Copy link
Contributor

commented May 5, 2018

Caching may be needed in some cases, but I wouldn't bother with it for a first implementation. A gitea instance run by an individual or small organization may not have enough issues in their db to cause a problem. If performance is still a concern, make global search an admin tool only, or add a config option to turn the global search feature off.

In my own case, global issue search is one of the first things I went looking for, which led me here. Seems like a gitea admin would need at least a global view of issues, similar to the global view of repos in /admin. Among other things, this would allow them to see how well gitea is being adopted so they can help bring project teams up to speed.

@stevegt

This comment has been minimized.

Copy link
Contributor

commented Jun 23, 2018

#3841 (possible dup) discusses how the web frontend for this might look.

@scullhead

This comment has been minimized.

Copy link

commented Jun 25, 2018

Here is my content from the issue #3841

  • Gitea version (or commit ref): 1.4.0+3-g641d481
  • Git version: 2.7.4
  • Operating system: Ubuntu 16.04.4 LTS
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant

Description

When you are on the "issues" tab of a repository you have a search input field where it is possible to search for a text in all issues of this repo.

When you klick on "Issues" in the global navigation menu of gitea it shows a list of all issues from all repositories (if they are public).
It would be very useful if there was also a search input field to search over all public issues.

gitea_issues_global_search

@stevegt

This comment has been minimized.

Copy link
Contributor

commented Jul 5, 2018

Here's a possible workaround until global issues search is available, but it only really works for new installs and internal teams: Our local Gitea install so far hosts dozens of projects and growing. Early on, we realized that we need to be able to see who is working on what in some global way to keep interns from running out of things to do. ;-)

As a workaround, we've wound up filing all issues for all projects in one general/issues repository instead of in their proper repos -- not great, but at least it gives us a quick way to see issue lists by assignee.

@stale

This comment has been minimized.

Copy link

commented Jan 20, 2019

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.

@stale stale bot added the stale label Jan 20, 2019

@lunny

This comment has been minimized.

Copy link
Member Author

commented Jan 20, 2019

We need a search result UI design.

@stale stale bot removed the stale label Jan 20, 2019

@stale

This comment has been minimized.

Copy link

commented Mar 21, 2019

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.

@stale stale bot added the stale label Mar 21, 2019

@lunny lunny added reviewed/confirmed and removed stale labels Mar 21, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.