#110: Use product prefix in ticket queries
---------------------------+-----------------------------------------------
Reporter: olemis | Owner: olemis
Type: enhancement | Status: accepted
Priority: blocker | Milestone: Release 2
Component: multiproduct | Version:
Resolution: | Keywords: ticket query product custom field
---------------------------+-----------------------------------------------
Changes (by olemis):
* status: new => accepted
* owner: nobody => olemis
* priority: major => blocker
Old description:
> At present product names are used by query module in order to match
> tickets . IMO this is not a good practice considering the fact that [#108
> name might change but prefix should be immutable] . As a consequence e.g.
> saved queries might need to be update if product name is changed. IMO a
> better solution involves using product prefix (e.g.
> `status=!closed&product=bh` ) . Nonetheless it'd be nice to keep
> displaying product name in select controls in web UI .
New description:
At present product names are used by query module in order to match
tickets . IMO this is not a good practice considering the fact that
[ticket:108 name might change but prefix should be immutable] . As a
consequence e.g. saved queries might need to be update if product name is
changed. IMO a better solution involves using product prefix (e.g.
`status=!closed&product=bh` ) . Nonetheless it'd be nice to keep
displaying product name in select controls in web UI .
--
Comment:
Accepting this ticket due to the fact that this needs to be finished in
order to filter products timeline in the way specified in #94 .
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/110#comment:2>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
