You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There may be an advanced use case worth supporting where we want to fill a board with a custom list of bugs. These bugs may span multiple products or just fall into some very specific search criteria that we otherwise don't support filtering on.
This is a pretty niche use case, so building a UI to support this does not seem worth the effort. And would confuse the simple product and milestone use case we currently support and encourage. But if it were an advanced only thing controllable via the page URL, I could get behind that.
To do this we could leverage the existing Bugzilla quicksearch language. So a custom board page URL might look like:
e.g. index.html?quicksearch=ALL%20prod:foo,bar
And then internally it passes the quicksearch param value through to the REST API and the results are put on the board as normal:
e.g. /rest.cgi/bug?quicksearch=ALL%20prod:foo,bar
The text was updated successfully, but these errors were encountered:
There may be an advanced use case worth supporting where we want to fill a board with a custom list of bugs. These bugs may span multiple products or just fall into some very specific search criteria that we otherwise don't support filtering on.
This is a pretty niche use case, so building a UI to support this does not seem worth the effort. And would confuse the simple product and milestone use case we currently support and encourage. But if it were an advanced only thing controllable via the page URL, I could get behind that.
To do this we could leverage the existing Bugzilla quicksearch language. So a custom board page URL might look like:
e.g.
index.html?quicksearch=ALL%20prod:foo,bar
And then internally it passes the
quicksearch
param value through to the REST API and the results are put on the board as normal:e.g.
/rest.cgi/bug?quicksearch=ALL%20prod:foo,bar
The text was updated successfully, but these errors were encountered: