Khadhar Mohaideen Oct 08, 2018. I have a requirement where we want to introduce Features as an issue type with the hierarchy of Epic --> Feature ---> Story ---> Sub-tasks., where we should be able to link Features as children of Epic and Stories as children of Features (with a filed similar to "Epic Link", such as "Feature Link" which linksTask is a very generalised word, just "someone needs to make some effort to do this". Jira Software's hierarchy is. Epic; Standard Issue Types (Story for example, but Bug, Improvement, and a couple of others are created by default in Jira) Sub-task Issue Types (Technical task and sub-task are the ones you'll see off-the-shelf in Jira)
If so, go into issues > issue type hierarchy. That said, this isn’t great practice in Jira. Think of Epics in Jira as Features in SAFe, then Initiatives in Jira as Epics in Safe. You can opt into the epic renaming beta, or just get your people used to the (truly aggravating) terminology mismatch. I actually did a whole piece about this today
However, there's a bug in most recent version of Jira Cloud that in fact allows you to do this. Steps to reproduce: Create an Epic. Create one or more Story or Task within it. Make sure they're linked to Epic. Convert this Story / Task into Epic. Jira should invalidate relation when changing Story or Task to an Epic, but due to bug it don't do
I have defined a Jira Project with a number of Initiatives. Under each Initiative, there is a number of Epics that originate from different Jira Projects. Under each Epic, there are tasks that come from different Jira Projects. I am struggling to find a query that will dynamically list all of the Epics and Tasks that are added to the Initiatives.
w4nc3. 299 183 25 397 69 365 248 299 361