What is the best way to track customer demand for features or bug fixes?
A user has requested that we add a field that can track how often a customer contacts about an issue, bug, or feature request. They could then log it onto the story that relates.
The voting feature would be great but it only allows one vote per user so we wouldn't be able to vote on behalf of the customer. A custom field is the only thing I can think of right now.
This can be accomplished in a couple of ways:
Thank you for your response. This will definitely work for grouping related stories and bugs.
We won't necessarily have a new story every time a customer contacts about an issue though. If it is a known feature request or bug that already has a story built out to capture the details, we wouldn't create a new one. We just want to keep a tally of how many customer have contacted about it.
Earlier, I was thinking of suggesting a "Number" custom field that you can increment anytime (through the Edit screen or a transition) but I am personally against this option. Let's say I have a ticket named "Feature 1", then 2 users have said the same thing. I will go ahead and increment a custom field named "Hits" to 2. Then another 3 came up, update it againt to "5" and so on. If I will go back and review this issue, where's the traceability? Who are these 5 users that just voted for mentioned "Feature 1"? When did they mention it? Is it still relevant or up to date?
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs