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 am working on custom issue hierarchy.
I created a new hierarchy called 'Initiative' and added a 'Parent Link' field to my issue screen. Now, the problem is, under 'Initiative,' I have a button 'Create Subtask.' I googled and users suggest creating a new project for the Initiative. However, this absolutely does not make sense for me. I already have an existing project with approximately 800 issues. Is it possible to change my current scheme so that only epics can be created under 'Initiative'? or to remvoe this button from initative?
In addition, I will add one more level above initative so this configuration should be applicable there as well.
No this can't be done.
There is an opren request for this, see JRACLOUD-7990
Or you will have to look at marketplace apps, like;
For me, I always use a separate project, for levels above Epic, in a hierarchy.
This will allow to use a different Issue Type Scheme, to limit the issue types available.
I have a project with 800 issues. So the only way for me to tackle this issue is to create a new project and move all the issues to the new project? This will take weeks to move everything manually. Is there a way to bulk move all the fields, issues, configurations, and screens to the new project?
How should I approach this problem? I don't know
Just make a new project, use the option to share the configuration with your current project.
The new project should have the same schemes as the current project you are using, if the the is a company managed project
Make a new Issue Type scheme with only type "Initiative", associate this with the new project.
Then JQL all you Initiative in the current project and make a bulk change, move all issue to the new project.
Make sure you also set the same permissions on both project, to retain the parent link information.