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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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
4,466,075
Community Members
 
Community Events
176
Community Groups

Linking ideas, creating sub-ideas

Hi Everyone,

We're new to Jira Product Delivery. We're an IoT technology provider company, with end to end (this is an important aspect with respect to what follows) services, from the device embedded part to the backends services.

We are thinking about using Jira Product Disccovery. 

Several questions we have so far:

  • What would be the most convenient mean to organize and structure the ideas based on our system architecture (we don't want a flat presentation of all the ideas concerning the system). Would it be to have as many projects as we have agents in our system?
  • As we're having end to end ideas, we may have sub-ideas linked to this idea. One system idea may have impacts on several components of the system. Is that an existing (or planned) feature in JPD?
  • On a more general aspect, is there a mean to link ideas between them, based on arbitrrary criterias that we would have the latitude to define?

Thanks in advance for any feedback and sorry if these questions are trivial.

Issam

2 answers

2 accepted

1 vote
Answer accepted

Hi Issam, 

It appears Tanguy has 'nested' ideas on the roadmap, according to his answer here: https://community.atlassian.com/t5/Jira-Product-Discovery-questions/How-to-group-nest-ideas/qaq-p/1872054

Jonathan

Was helpful thanks Jonathan.

Issam

1 vote
Answer accepted

Welcome Issam, I can only give you some insights as a JPD user, hope it's helpful.

What would be the most convenient mean to organize and structure the ideas ... we don't want a flat presentation of all the ideas

We implemented a custom field called "Problem Area" which allows us to bucket ideas into larger areas to act almost like a Problem Epic of sorts. We can then create filtered views based on that field, and/or group the views by Problem Area. For context, we don't use JPD to gather "Ideas", we use them to gather, understand, and prioritise problems that we would like to move into ideation.

You could achieve the same with labels, or other types of fields too.

As we're having end to end ideas, we may have sub-ideas linked to this idea

We were also looking for this functionality, but it appears there's no hierarchy to ideas. This would help us as sometimes an idea might be so large that it needs to be broken down into smaller ideas but you still want to be able to keep the relation.

This is possible in a number of products similar to JPD.

On a more general aspect, is there a mean to link ideas between them, based on arbitrrary criterias that we would have the latitude to define?

JPD is essentially Jira under the hood, which means an Idea can be linked to other ideas (or anything else in Jira) just like you would normally. You have control over the link types. I don't believe you can control the criteria, but I'm no automation wizard.

Hi Jake,
Thks for the feedback, it actually helps.

Issam

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events