Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

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!




We would like to be able to have some sort of Sub items so we can track experiments and MVPs we are trying for big features we are building 

For example we have a feature like integrate with Google Docs.... the fist sub task might be read only integration with Google Sheets...etc?

Is this part of your vision for the product



2 answers

Suggest an answer

Log in or Sign up to answer
2 votes
Hermance NDounga
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jul 20, 2022

Hello Jerry, 

We currently do not have different issue types or issue type hierarchy in Jira Product Discovery (mentioned in the post Known limitations), but it is in our roadmap. 

In the meantime, as mentioned by Minesh, the easiest way to track operational chunks of work would be to create Epics and/or issues from the Delivery tab of an idea.
Note that if you don't own Jira Software, hence do not have Software projects template in your site, you could still use Business projects, provided in all Jira sites. When you create a project, you can find them under "Work Management", even if you only have Jira Product Discovery enabled on your site. 

If you need something less formal, you can simply add checkboxes to your idea description in order to list the subsequent tasks to do in this idea - this is more to get a "to-do list" rather than a proper tracking system. 

Finally, Tanguy created a short video on how to create an Opportunity/Solution relationship between ideas. You might be inspired by this workaround for your specific use case. 



Using your example, sounds like you have an idea and you want to evaluate if you are on the right track. If that’s the case then we typically run experiments to validate and wait to build it out until we have a level of confidence. 

if you want to track the execution of the idea, the best way I handle it is using epics for each sub-idea and set the priority of those sub-ideas as I see fit. 

adding sub-ideas does not sound intuitive to me. 

AUG Leaders

Atlassian Community Events