We're reviewing some processes at our organization and I believe the way we track and display our product feature requests could benefit from a refresh! I'd love to hear ideas or implementations that have worked for other organizations.
We make software products. We collect feature requests internally, primarily from our customer-facing teams who submit feature requests on behalf of the customers they represent, but also occasionally from our Product team.
Often, we have redundant requests or similar requests, and refinement takes a long time. The requesting teams are responsible for browsing already submitted requests before submitting a new ticket, but this process is time-consuming and often difficult for individuals not as familiar with navigation and querying in Jira.
I'm looking for suggestions on how to make that part simpler.
Other information that may be relevant:
The teams responsible for submitting feature requests and our product stakeholders can access a resource where they can quickly find existing feature requests submitted, identify related requests, and pull reports on feature request metrics without requiring strong JQL skills.
Please let me know if you have any ideas, or if you solved a similar issue at your organization. Displaying searchable issues in Confluence pages, Jira Dashboard gadgets, Kanban Boards, Structure -- I'm open to consider any ideas! Thanks for your thoughts.
Catch up with Atlassian Product Managers in our 2020 Demo Den round-up! From Advanced Roadmaps to Code in Jira to Next-Gen Workflows, check out the videos below to help up-level your work in the new ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events