nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Can we restrict issue types when using linked issues

M Vijay Kumar

Hi Team,

We are trying not to use Jira out of box Hierarchy Levels instead we thought to have Epics, Features, User stories and Tasks as Hierarchy Levels. Can confirm these cannot be achieved through out of box, we are using linked issues ( using relates to and relates by). One thing which i am looking into, when I create EPICS can i restrict to show only features in linked issues search field. This cannot be done through Jira out of box features can this be implemented using any Add-ons ?

Please do let us know if this functionality can be achieved.

Thanks,

Accepted answers

All comments

Ste Wright

Hi @M Vijay Kumar

Not that I know of - you'd need an add-on such as Extended Schemes for Jira

Personally, I think using linked issues can get confusing and you're limited when doing reporting as they're not parent / child relationships. You could name them that (parent of / child of) but they're treated as sibling relationships.

I would advise getting an add-on to allow for additional levels in the hierarchy - such as Portfolio

Ste

M Vijay Kumar

Hi Stephen,

Yes agree to your point, but the issue with Portfolio is that any level you can have is on top of EPIC and stories and Tasks would be at the same level, but the way we are looking into is ( EPIC is at the top level) followed by Features which has user stories followed by Tasks under stories.

Can you brief on reporting limitations if we follow the hierarchy level which I mentioned over there.

Thanks,

Ste Wright

Hi VJ,

For tasks below stories, an option would be to rename sub-tasks to task? Or add an additional sub-task type?

For Epics above Features it's a little trickier - you could consider an app such as this SAFe translator - or do it yourself using instructions such as this answer

And if you want to combine both needs - you could consider an app like Structure?

We've had the linked issues approach in an instance before - we just found creating the reports and JQL more arduous because it's not using a hierarchical approach. Plus it was a little more difficult to get reports with subordinates to show appropriately.

Ste

M Vijay Kumar

Hi Stephen,

Really appreciate your responses.

1. Agree with story to sub-task which even we are considering as an alternative

2. Browsed through SAFe Translator renaming Epics to Features would help ( Features-> stories-> Sub-Tasks ), but how about actual EPIC which is parent of feature ( Should I go for Portfolio in this case ?)

3. On Structures, how do set I hierarchy ( I cannot manually create structures every time i add issues ( features, stories and sub-tasks) and hence I need to depend on Generators to automatically create structure [ EPICS-> FEATURES-> STORIES-> SUB-TASKS] in this case what would be the option apart from Linked Issues, as I was able to achieve this hence the question raised on how to restrict issue type on Linked issues so that I can link only features under epics and stories under features. Any idea on this ??

Thanks,

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira

jira-server