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
I have Advanced Roadmap and set-up Initiative on a level above Epic.
Is there a way i can prevent sub-tasks getting created under Initiative?
Can we prevent Initiative getting created under Epic via button "Create Issue in Epic"?
Hello @Vishal Biyani ,
To prevent the creation of subtasks under an Initiative issue type, would be to create an initiative specific project that only contains the initiative issue type as described in the documentation "Configuring hierarchy levels" under the section "Ways to set up the initiative level in plans" for Adding the initiative level to multiple projects, noting the setup is generally recommended for a cross-project organization it doubles with the use case you described:
An issue can live in a single Jira Software project. However, if your organization is working on cross-project initiatives, you might find it useful to create a dedicated project that gives you a high-level view across different streams of work.
If you set up the initiative project with the initiative issue types only and no sub-task issue types then the subtasks will not be an available option for creation under the initiative.
However, the second request to preventing Initiative from getting created under Epic is a Bug we are tracking at the following links for both the cloud and server platform respectively, make sure to add yourself as a watcher to get updates on the status:
There is a workaround mentioned on the Bug for how to identify the issues and correct via a bulk update that has both a parent Epic and are of an initiative issue type using the JQL:
issuetype = "initiative" AND "Epic Link" is not EMPTY
But one thing to keep in mind is that the filter will need to be regularly checked for additional issues that fall into this state by mistake, so an additional workaround to making tracking and identifying these is to save the above JQL as a filter and then set the filter to an issue filter macro on your dashboard so you are shown any issues that may need correction on login.
I think the scenario you are looking for is only available when you use SAFe and install the SAFe plugin for Jira.
Otherwise your issue types if you added them to your instance will be just like any other issue type "under" Epic