How to "count" customer feature requests?

[Alex Harr]

My team and I wanted a way to track customer feature requests so I created a new issue type called "Customer Requests". Every time a request comes in from customer calls, I log it within JIRA. 

What I would like to do is essentially count the number of similar requests so we can understand what feature we should place on the roadmap.

Any recommendations?

[Bill Sheboy · Accepted solution]

Hi @Alex Harr  -- Welcome to the Atlassian Community!

What do you mean by "count the number of similar requests"?  Would this be all of the requests or some piece of information in the requests, such as key words in the summary/title?

Best regards,

Bill

[Alex Harr]

Hi Bill!

For example, say if customer x requested to have a download csv button for a table of values. Then two days later customer y comes along and also requests the same button. I would then like to have the running count of that csv button feature request, so for this example, it would be 2.

Thanks!

[Bill Sheboy]

Thanks for explaining, Alex.

Solving your counting question depends on how you are adding or "intaking" new requests.  If you just add them with no other data, there is no easy way in Jira to see patterns.  For example, it would be cool if there was a word cloud gadget to see patterns, but there is nothing built-in to do that.  (You can probably buy one on the marketplace...)

If instead you pause and think about your product and domain, and identify areas of interest. Then as you add your customer requests to Jira, you could add one or more Labels to flag the interest area.  Then you can report on the Labels and counts, such as with a 2-dimensional filter or pie chart gadgets on a dashboard.

Here is some documentation on dashboards to get you started:

https://support.atlassian.com/jira-cloud-administration/docs/configure-custom-dashboards/

https://support.atlassian.com/jira-cloud-administration/docs/use-dashboard-gadgets/

https://confluence.atlassian.com/display/GADGETS/All+Atlassian+Gadgets

[Daniel Ebers]

Hi Alex,

many good information were already given here.

It depends a bit on how complex the implementation should look like.
You could take Atlassian with jira.atlassian.com as an example.

The feature used there are "Votes" (please see here for further information) also a good feature might be "Watchers".

The advantage is that this feature is available right away. The disadvantage might be that it is not so powerful compared to what Clark and Bill recommended.

In any case, you can link issues. This is also done with Atlassian when time shows that two separate ideas were basically the same (along with similar cases).

Cheers,
Daniel

[Clark Everson]

The best way to do this is with script runner

https://community.atlassian.com/t5/Jira-questions/Count-number-of-reported-issues-based-on-Epic-Link/qaq-p/747886

you could also have an epic that ties all these features in and shows total count, though epics are designed to close eventually

https://community.atlassian.com/t5/Jira-questions/How-to-get-Issue-count-per-Epic/qaq-p/1166624