I have multiple "Features" and to that multiple "Features" there are multiple "Stories" linked to them. These multiple "Features" are linked to an "Epic". Now I need to find the linked issues of those multiple "Features". I'm able to get linked issues of a single "Feature" by using the JQL ( issue in linkedissues (ABC-123) ). But I want to get linked issues of multiple "Features". So, I tried with the JQL ( issue in linkedissues("ABC-123", "ABC-246", "ABC-456") ). But now this one fails to get the linked issues of those multiple "Features".
There's going to be benefits in...
Is there a reason you chose not to do this, given it can cause issues like the one you're facing?
@Stephen Wright _Elabor8_ Yeah Stephen, There is reason we choosed to do so. We are having a multiple stream which we are defining them as an "Epic" and under those streams we are developing multiple "Features" . I have gone through the Advanced roadmaps and as there is an limitation that we can only show Epic > Story > Sub-task in the hierarchy level. So thought if we could bring that down into JQL we can have two dashboards where one shows the "Epics" and the "Features" linked to it. Another dashboard shows the "Stories" and " Subtask" to it . Even if we able to show them till "Stories" will work for us. Please help me to solve this .
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event