We're exploring new ways for our team to submit bugs and feature requests. We're requesting Jira users (e.g. account management) to submit a Jira ticket for each request. We understand there will be duplicates. In fact, for a variety of reasons, we want the additional context duplication can offer us. We'd like this duplicity to help drive prioritization (i.e. "Customers X, Y, and Z have requested this Feature 123! We should move this up in the backlog accordingly.").
Assuming I tag the issues manually as "duplicates" in the Linked Issue field, my idea was to create a filter that would tag the original as issue "is duplicated by" and then apply "duplicates" to any follow-on issue. I would then create a filter that eliminated the "duplicates".
None of my JQL queries are working (new to JQL/SQL) and most forum postings assume I'm trying to find and close duplicates when the original issue is completed. #nohelp
Questions:
a) Better idea here than using duplicates to drive backlog prioritization by multiple stakeholders? (NOTE: See item below about "voting". It won't work as is.)
b) Which JQL query is right for this filter?
NOTE: Unfortunately, using the voting functionality won't work, because it's limited to one vote per Jira user (e.g. account manager) and he/she may have multiple customers requesting the feature.
