Use search to find the issue (this is painful in our experience)Īdd a comment with the feedback and other information They would then find the relevant issue in Jira and paste the feedback into it.įirst, you have to manually copy the feedback. Someone-perhaps a product manager or someone on the Customer Success team-would copy feature ideas from your support tool, CRM, email, or wherever it comes in.
#JIRA CLIENT FACING TIME REPORTS MANUAL#
Collect product feedback from all channelsĬollecting feedback in Jira is a manual process. We’ll compare and contrast with Savio to provide some sense of where Jira works best and where it falls a bit flat. Let’s see how a tracking system using Jira fares against this list. Prioritize and sort by basics like number of feedback customer attributes Whatever tool you use, you want to make sure your feature request tracking system is able to do the following:Ĭollect product feedback from all their channels with little to no painĬategorize and organize feedback to understand what customers are asking for What you need in a feature request and bug tracking system It also could be a bit cheaper to minimize tools. It means minimal changes to process and your product management and development teams already have access.
Using your dev tool for feature requests means that you don’t have to find or learn a new one. Adding tools to your stack adds some complexity.
There’s a kind of logistic ease in using the same tool for both planning and building processes. So it might make sense to keep requests there too. Your Dev team is going to use Jira (or another dev tool) to organize the process of building features. You want to keep requests in the same tool that your development team uses to build the features. Jira isn’t a feature request tracking tool… so why would you use it as one? There are a few reasons. Whatever you do, track your feature requests
#JIRA CLIENT FACING TIME REPORTS HOW TO#
How to best use Jira to track feature requests The pros and cons of Jira for tracking feature requests In this article, we cover the pros and cons of using a Dev tool like Jira to track feature requests. There are even some good reasons why it might be the tool of choice.īut it’s worth considering the limitations of Jira so that you can understand where your system is most likely to break down. You can create a feature request tracking system that works using Jira. That doesn’t mean you shouldn’t use Jira-or another Dev tool-to track customer feedback and feature requests. I’ve heard this, or variations of this, literally dozens of times when talking to Product and Customer Success teams. “Jira is where feature requests go to die.”
0 kommentar(er)
