You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I'm working in the discovery project. My colleagues submit ideas all the time and the product team triages them. Sometimes, we will get ideas that will eventually be the epic and other times we get ideas that are really only singular story tickets. We need to track these though.
I see the option to link and we have "is child of" and "is parent of" but it doesn't make any visual changes to the list of idea tickets. Is there a way to make an idea subordinate to another? Indenting the child issue on the list page?
Hi @Abby Kiesling ,
You can use the epic->story/task dependency to reflect that hierarchy. You can also check some addons in the Atlassian Marketplace, like Structure: https://wiki.almworks.com/documentation/structure/latest/data-center-and-server/getting-started-with-structure-32223517.html
Please see my reply to Mark. Jira won't let me post a reply to you saying the same thing. haha
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Abby Kiesling - If this is purely to provide a visual representation of hierarchical ideas in an outline, Jira is not designed for this. In its simplest form, Jira has a designed hierarchy of Epic >> Story/Task/Bug >> Sub-Task. Epics can present children in a containerized form and sub-tasks can appear as children of Stories/Tasks/Bugs.
There is also the concept of Advanced Roadmaps which will expand the issue type-based hierarchy to go higher than the Epic so that you can show objective level requirements all the way down to sub-task.
For displaying ideas in some type of hierarchy, you'll either need to consider adjusting how they map to issue types or consider a marketplace app.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Apologies, I wasn't specific enough. I am talking specifically around Discovery projects and Idea tickets.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Got it - So, you're using the new Jira Product Discovery? I don't have much experience with that one other than some demos I've sat through. I'd need to defer to someone else on what's possible.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.