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!


Can I configure project so can't create Initiatives but can add Parent Link to an Initiative

I have created a new issue type and hierarchy level above Epic called Initiative.  Initiatives are for cross project work.  I thought if I just added the Initiative issue type to the 'Cross project' Jira Project, that Initiaves could be created in that project (that all works ok) but I wanted other projects to be able to add Initiave Parent Links to their Epics (i.e. link their Epics to cross project Initiaties) but NOT create initiatives themselves.  The reason for that is that if they create their own PRoject Initiatives and make them parents of their Epics, the Epics cannot then be children of the 'Cross Project' Initiaves. Is that possible ?


2 answers

1 accepted

1 vote
Answer accepted

This is solved. It is possible to configure as desired.  Projects do not need to have Initiatives in their Issue type scheme to make their Epics children of other projects Epics

Yes, you can use the initiatives across all projects in your instance without adding the initiatives in all projects. This is how the roadmap plans hierarchy works.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events