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

Allow "all" option in multiple select field for repositories to search with lucene #584

Open
gitblit opened this issue Aug 12, 2015 · 8 comments

Comments

@gitblit
Copy link
Collaborator

gitblit commented Aug 12, 2015

Originally reported on Google Code with ID 288

What version of the product are you using? On what operating system?
GitBlit v1.3.1

It would be a nice feature to be able to search all repositories by default. So, adding
an option "all" and making it default option would, in most cases, save a click or
two.

Background: I want to implement a search button for commits in a JIRA issue. For that
the form fields will be filled automatically and it would be easier if there is an
"all" option.

What do you think?




Reported by stephan.krull.ecg on 2013-08-05 13:59:35

@gitblit
Copy link
Collaborator Author

gitblit commented Aug 12, 2015

It's a good idea.

Reported by James.Moger on 2013-08-05 14:24:30

  • Status changed: Accepted
  • Labels added: Milestone-1.4.0

@gitblit
Copy link
Collaborator Author

gitblit commented Aug 12, 2015

Reported by James.Moger on 2014-02-04 03:35:14

  • Labels added: Milestone-1.5.0
  • Labels removed: Milestone-1.4.0

@gitblit
Copy link
Collaborator Author

gitblit commented Aug 12, 2015

Reported by James.Moger on 2014-03-11 19:45:28

  • Labels added: Milestone-1.6.0
  • Labels removed: Milestone-1.5.0

@gitblit
Copy link
Collaborator Author

gitblit commented Aug 12, 2015

Reported by James.Moger on 2014-05-05 17:57:34

  • Labels removed: Milestone-1.6.0

@gitblit
Copy link
Collaborator Author

gitblit commented Aug 12, 2015

When reading issue #769 it seems like the wildcard patch could be part of a solution
for this issue. @James Moger: Can you confirm a correlation?

Reported by stephan.krull.ecg on 2014-09-11 07:35:45

@gitblit
Copy link
Collaborator Author

gitblit commented Aug 12, 2015

As far as I can tell the wildcard patch breaks standard branch indexing; it drops specified
non-wildcard branches.  It also has 0 unit tests and is part of a series of completely
unrelated changes.  I won't be merging pr-211 anytime soon.

Reported by James.Moger on 2014-09-11 13:54:10

@gitblit
Copy link
Collaborator Author

gitblit commented Aug 12, 2015

Issue 829 has been merged into this issue.

Reported by James.Moger on 2015-02-26 13:46:30

@flaix
Copy link
Member

flaix commented Dec 13, 2016

@gitblit, This sounds like it has been implemented in pull request #935.

@krulls, does this work for you in v1.7.0?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants