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

"Ideas Taxonomy" i.e. connecting ideas back to the product vision and business initiatives.

Do you have plans to define a taxonomy for "ideas"? I mean... if someone presents an idea, I'm curious about how the idea can explain its relationship with the:

- Vision
- Mission
- Goals/Objectives
- Strategies
- Tactics
- Objectives

I'll admit, I think I'm still trying to figure out how the capturing of ideas works in regard to connecting them back to the business initiatives or themes. I'll just keep exploring the JPD product in the meantime. Thanks in advance for your reply!

1 answer

I am struggling with a bit of this as well. High level goals and objectives can be captured by the various "Select" fields you can create. You might be able to setup a chain of automation that connects the relationships if they are that linear for you?

However I am really struggling with problems/opportunities. They say you can use an idea issue type to represent both "ideas" and "problems", but they are two very different things to me. An idea is a proposed solution to a problem. I might have multiple ideas for any given problem that I want to explore and rank. It seems like I need two different issue types for this. I would collect feedback on both as well. Insights to prove the pervasiveness of impact of the problem and insights on the desire for the solution if.

I guess I could use fields to manage this as well, but I don't want to see my problems in the same list as my ideas and when looking at my ideas I want to clearly see what problems they are assigned to.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events