Collect and organise feature requests

[Sharon Anderson]

I am looking at a way to collect and organise feature requests for software development.

I don't want to add these requests to my current project backlog as it would be a nightmare to groom.

It would be great to be able to record who has requested it and have the ability to vote based on customer feedback.

I would need to be able to add a component so grouping and filtering becomes simple

[Kirstin Seidel-Gebert · Accepted solution]

Hi Sharon,

we have a separate project for product management where we collect new features. If a feature will be implemented, we clone the product management issue to the dedicated development project, so that the two issues are linked.

Cheers,

Kirstin

[Alessandro Mastrogiacomo]

Hi Kristin! I’m interested in this. So each product you clone twice? One for business request, features, etc. etc. and one for product development? Or you have a separate container project where you keep all the request and features maybe labeled for project and then move the issue to its related backlog?

Thanks!

[Kirstin Seidel-Gebert]

We have one product management project where we collect all major feature request throughout all products.
The workflow is:

The product the issue refers to is indicated by the component. If the feature requires changes to multiple products, we create sub-tasks.

Cheers,
Kirstin

[Sharon Anderson]

Thanks Kirstin. Do you set this up in a Kanban board?

[Kirstin Seidel-Gebert]

I'm not sure how they manage their tasks. Probably in a Kanban board, yes.

[Irina_Bel_Stiltsoft_]

You can create a public forum that is mapped to a relevant Jira project with the Customer Case for Jira app. Also, you can make it a private one by restricting it to specific email domains and emails. Your customers and team members will be able to add votes for feature requests to make it easier for product people to prioritize them. You can also use a component field on a request form to make it easier to filter tickets.