I have the scrum teams using Epic for different purposes. I have to track the Program at Initiative and Feature roll up. Can I directly link scrum level user stories to my features and skip the scrum board epic for Program roll up and roadmap?
You can - as a Site Admin you can:
^ Notably this changes the hierarchical configuration for everyone across your instance, this isn't a project-by-project structure.
I would be hesitant to remove Epics from your overall hierarchy - there are benefits Epics offer such as Epics Panel, Epics Burndown, etc which you will lose.
What is the intent of linking direct to the next level up? What do you use Epics for instead?
For the executive roadmap I am ok to not go into an epic level - I can just show them how work (User story level) is feeding into their key initiatives > Features
For the Program level management at the release level - I plan to use the Release tag from the user story / the link to the feature on the program board to discuss progress.
I am losing one level of granularity, which at this point I don't have any audience for.
Thanks for your Information,
But I am facing a problem when tried to follow your Hierarchy and the issue is;
I have Parent Link field in Story Screen and removed Epic Link as i am not going to use Epic in my projects. When the Epic Link is removed, I am not getting my Parent Link Field enabled to link any feature. At the same time when I include the Epic Link in my story screen and leave it blank then I can add the Feature link to Story.
Is there any way to enable parent Link without including the Epic Link in the story screen?
It will let you have Parent Link without Epic Link on the story screen - make sure you have:
These are the steps I took to test it works just now on both Cloud and Server.
We know that great teams require amazing project management chops. It's no surprise that great teams who use Jira have strong project managers, effective workflows, and secrets that bring planning ...