Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How to create dependency between jiras which are just related and should happen in concurrency

I am creating a big project plan and it has different stories which have dependencies.  I see there are 2 types of dependencies. 

1) Sequencial where one story can only start after the dependent story is done and that is supported

2) stories which need to be performed in parallel

Is there any guidelines on how to enter such data in an advanced roadmap ? Does the tool support different type of dependency in same plan and how the warnings and red colour appear ?


Kind Regards


1 answer

0 votes

Hello @manas Sahoo ,

The Dependencies are tied to the 'Blocks/is blocked by' issue link by default, and Advanced Roadmaps, looks at the link types to be loaded and considered either Concurrent or Sequential and there is not a hybrid option, to show a combination of both.  So a total "Either-Or" situation,  you can either work on the issues in parallel or you cannot and therefore require sequential work.

The intent is to set up restrictions in the plans with an option to either do ad-hoc or scheduled work and in all cases as a process dictates that the blocking issue must be completed before work can start should not be conditional in a hybrid approach. 

In a working example on issues if there a need to have a blocker in a portion of the work but some work can be done in parallel the process of having the dependant issue sequential should remain as a blocker without the option to circumvent but rather breaking out the workable portion in parallel as a separate issue.

But looking at this it sounds like you are trying to get a better visual reference of related issues, opposed to just blockers, and for this, I would suggest looking at "Coloring options" and "Issue groupings" that can be used to visualize the relations based on either a component, label, or custom field.  you could further automate this by having project automation add a value to the field of choice contingent on the link type associated. 

Additional details on automation can be seen in:


Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Advanced Roadmaps

Introducing Advanced Roadmap’s new dependency report

To see this feature in action check out our recent dependencies demo here: Keeping on top of your dependencies is a key part of ensuring project success....

1,747 views 12 18
Read article

Community Events

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

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you