Story ordering based one dependency in product backlog

[unnikrishnan]

Hi All,

We have the complete product backlog with different section such as ready of grooming ,ready for development etc. We do the link the interdependent tickets using the the link option and specify what sort of the relation the ticket between such as block, blocked by etc. After the big project complete story mapping, we need to look inside the ticket to see the relation.However do we have any option to Block the incorrect ordering of the ticket when we violate the dependency defined between stories.For example Story1 ,2,3 are there and Story 2 can start only after finishing  Story 3.So As a PO , Jira should not allow us to order  1->2->3  as it breaks the relation . We need to be allowed only 1->3->2.

[Ivan Lima]

Hi @unnikrishnan, you are relating your "ordering" of issues with the issue links you've created. Assuming you're ordering your backlog using ranking, and Jira Cloud does have an API to Rank Issues, as well as to get the ranked issues in a given board, you should be able to achieve this using an add-on/script.

However, it looks like a lot of work to implement it as you described. I know it's not a direct answer/solution for your question, but I would certainly look at alternatives such as leveraging swimlanes to highlight the ones you would need work on first, with no blocking dependency, for example. I am sure that there are many other possible setups that you can explore to help you to get a similar outcome with way less effort. 

I'm now interested in seeing what others have experienced with a similar use case and also recommend reading on the link shared by nina.

I hope that helps.
IL.

[nina_schmidt]

Hi @unnikrishnan 

Perhaps some of the input Andy gave here might help: 

Link