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

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • 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

Can Easy Agile Roadmaps handle dependencies?

Let's say we have the epics A, B, C and D.  A and C can be worked in parallel, but it makes no sense to start B if A isn't finished.

Can I handle such dependencies in Easy Agile Roadmaps?

1 answer

1 accepted

0 votes
Answer accepted

Hi Evelin!

We don't yet have a feature to display dependencies in Easy Agile Roadmaps, but we're keen to learn more about your use case!

  • What level of planning does your roadmap visualise? A single team, a product or project, a team of teams, a program or portfolio of work?
  • Ideally, how would you like that dependency to be displayed? We've used connecting lines in another app that are coloured to represent healthy/blocking dependencies; would this meet your needs?
  • Would it be helpful or not to automatically move epic B if epic A is delayed, or just show a warning about the breaking dependency?

- Stephanie Seymour, Easy Agile

If you'd like to contact me by email, feel free to reach out at support@easyagile.com. 

Hi Stephanie,

To answer your questions:

  • We like to visualize two levels: 1 - epics of one project, and 2 - projects that we like to work at during the next year or so. I'm using project as a general term here. It can be the new version of an exiting product, stuff that is completely new, or even research - all of them cost personnel resources (which are limited).
  • The connecting lines that you describe would meet our needs, yes.
  • Moving dependend objects automatically would be helpful, yes. If a dependency breaks, a warning would be good, and a decision Move / Don't move. (I'm not sure if this will work out. The point is that some projects can be moved to a later time but others can't, and you need to be aware of this when rearranging them.)
  • But to see the dependencies at all would be a big advantage already. Moving dependencies automatically is no must.
Like Kristina McInerny likes this

Thanks for your feedback, Evelin!

I've made a note that dependencies and warnings about dependency health are the priority, as well as your comment about providing the option to move problem issues instead of moving them automatically.

Dependency links aren't on our short-term roadmap but I'll reach back out to you when we do have this feature available for you to try!

- Stephanie Seymour, Easy Agile

Like # people like this

Hi Stephanie,

+1 for dependencies with conecting lines (End to Start, End to End, Start to End, Start to Start) and warnings. Moving should be manual, or at least with undo.

BR,

Nik

Hi Nikolaus,

We are currently considering using Jira's "issue link" field, such as "blocks" or "is blocked by" to handle dependencies. Creating or deleting dependency lines on the Roadmap would then modify these fields. Additionally, if there are already issue links on your issues, these would pre-populate on the Roadmap.

Can I get a little more context about what "End to End" and "Start to Start" connecting lines would be used for? If Epic B depends on Epic A, would that be a "End to Start" line?

- Stephanie Seymour, Easy Agile

Like # people like this

Hi Stephanie,

quickly hooking in here, using Jira's "issue link" field sounds like a great addition which I would definitely appreciate. Even simple one-way population of such dependency lines from the issue link field would be good to have already.

In my understanding and usage, "A is blocked by B" would be an end-to-start dependency, but I see that this may definitely differ per user and project.

Cheers,
Tobi

Like Stephanie Seymour likes this

Hi Tobi, thanks for your feedback!

By one-way population, does that imply seeing dependencies that already exist but without being able to create new ones on the roadmap? I can see how this could make it easier for us to release this feature incrementally.

I've added another vote on your behalf to this issue. We're currently categorising this work as "Thinking about": we're gathering feedback like yours on how we can best go about providing value to customers and weighing it against other valuable tasks.

- Stephanie Seymour, Easy Agile

Hi Stephanie,

thanks for taking this into account!

Yes, in my opinion it would be already helpful to simply show dependencies in the Roadmap which have been created using the "issue link" field - so for you guys, simply parsing these fields and drawing the respective line would do the trick. Being able to do this the other way around, at least for our use case, would be lower-priority bonus features.

Cheers,
Tobi

Like # people like this

Thanks for the detail, Tobi. We use customer feedback to prioritise work so thanks for helping us with that challenge.

In the meantime, you can keep an eye on this feature on our public roadmap for Easy Agile Roadmaps. I'll also reply to this thread with any updates to keep you in the loop and get feedback on any new developments.

Cheers,
Stephanie

Hi @Stephanie Seymour  

 

Add one more to the request for dependencies based on Jira links. I think this tool would great for my organization, but the visualization of Jira issue links is a hard requirement for us. 

Hi Rory, 

Thanks for your vote, I've added that!

Kind regards,

~ Stephanie Seymour, Easy Agile 

Dependency visualisation would be great for us too. Please prioritise this feature as much as you can for us. Thank you!

Like Stephanie Seymour likes this

Hi Chris, thanks for your vote!

For those whose dependencies span across teams, another of our apps features dependencies: Easy Agile Programs shows dependencies at a team-of-teams level. If you’re looking to plan work across multiple teams, I recommend trialing it to see if it suits you and your teams!

Kind regards,
Nick Muldoon, Easy Agile

Like Stephanie Seymour likes this

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Marketplace Apps & Integrations

Do Not Lose your Customer’s Trust

Missing deadlines is one of the biggest problems every team lead wants to avoid when dealing with managed services. When the customer contracts your company to help with IT services it is expected th...

24 views 0 0
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