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
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
Hi, we are considering adding "Theme" hierarchy to our Jira and Plan. Theme is only beneficial to us, if we can set more than one Theme for an Initiative. Is that possible and how?
Hi @Dina M,
The older user interface for Advanced Roadmaps (known as Live Plans) had the concept of a themes that you could apply across multiple hierarchies of issues however we didn't include this in the new feature because the data was only accessible within a plan and it wasn't visible within the rest of Jira.
It really depends on what you want to do with this theme data. Our long term vision for replacing themes was to provide reporting options based on custom fields (to replicate the reporting that we had specifically for themes applied in plans). So my recommendation might be to just create a multi-select custom field called Theme and then use that on your issues.
Although we don't yet have the report features (and currently they aren't on our short term roadmap) this approach may be a good long term bet. It really depends on how you want to use that theme data? What are you hoping to gain from it? For example are you wanting to ensure that you're investing the right amount of effort on each theme?
@Dina M -
In AR, the parent/child hierarchy can only allow child issue to have one and only one parent. One parent can have multiple childs. Example - Epic A can only report to Initiative A, and cannot also be reporting to Initiative B.
However, you can Issue Link to multiple parents. The drawback is that AR will not reflect the issue link relationship in your plan.
Hope this helps.
Best, Joseph Chung Yin
Jira/JSM Functional Lead, Global Infrastructure Applications Team
Thank you, and it totally make sense except for Themes. I have seen multiple organizations struggling with this rule for specifically Themes. An initiative can drive more than one strategic outcome, and if I can't reflect it, then it is not usable.
Is their way to bring it up as a request to Atlassian to consider flexing this rule for specifically Themes?
You will need to submit a formal support request with Atlassian directly.
Just to make sure currently you are planning to add an issue type "Theme" in the hierarchy setup above "Initiative"? Because in the current AR interface (not Live Plan UI), the "Theme" was removed. In the older Live Plan UI, there is a Theme object for you to create reports.
One other idea is for you to utilize other fields (i.e. Component/s) where an issue can be associated with one or more values. You can then expose the field in your AR Plan, so you can group the issues.
Or....you could consider putting the "Themes" below Initiatives in the hierarchy. Not ideal, but possibly workable?