Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

What's the best way for presenting existing feature requests to internal stakeholders within Jira?


Hey there!

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:

  • Our feature request project is not currently a Jira Service Desk project, although we have JSD.
  • The feature request tickets are only viewable internally to employees and not to customers.
  • We may be open to a complete process re-design if one is required to enhance visibility of these tickets. (So get weird with your ideas! An overhaul is welcome in this case).
  • We use Jira Software and Confluence, as well as the Structure for Jira app. I'm mentioning that as I think there may be an opportunity to use this in our improved ticket visibility design, whatever that ends up being.


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.

3 answers

1 vote

Thanks, @Irina_Bel{Stiltsoft} ! This seems like a really solid option.




0 votes
Irina_Bel{Stiltsoft} Marketplace Partner Sep 28, 2022

I'm happy to be helpful:) 

0 votes
Irina_Bel{Stiltsoft} Marketplace Partner Sep 28, 2022

I have an idea for you. The Customer Case for Jira app meets your case since it's the app for creating forums. In your case, it's reasonable to create a public forum to let all your customers or team members create a feature request. A forum is mapped to the relevant project in Jira. All the tickets created via the forum are automatically shown in the relevant Jira project. When submitting a ticket, a form automatically checks whether tickets with a similar description already exist in the backlog to avoid creating another one with the same request.2022-09-28_15-57-59.png

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events