Tarun Sapra Atlassian Team

Hello @James C_ The team sprints on the Jira board can be created for future sprints for the current PI hence around 6. No future sprints need to be created for the future PI but for the ongoing PI, it's a good idea to create the future sprints on the jira team's board and let those sprints sync with the Anchor sprints…

Hello @James C_ Could you maybe validate if the sprints coming from the board of Team B have all the 6 sprints of the PI defined on them and these sprints are coming across in JIra Align and mapped to the anchor sprints. On the JIra board we can define future sprints, hence the best practices is to create all the 6 future…

Hello @Anne Leduc Thats a good question, yes we can use the "predecessor/successor" links when the number of teams are less, but as an RTE if you have 10 teams in your train and even if the dependencies are within the same ART/Program then Align supports some excellent views (grid, wheel view) apart from the information on…

This is a really helpful writeup @Sam Tsubota , thanks so much for sharing!

Hello @elaine_paton The use-case which you have defined, in this you can have feature B connected to the dependency object. And this use-case is more of a "work sequencing" issue instead of regular dependency management. The intent behind dependency management in Align is that teams collaborate together to deliver…

Hello @Bodo Stoecker As per the docs, below is the list of work items that support notifications via the discussion link - Though you can tag the relevant person in the chat section of the dependency and they are notified when they login to Align. So when the user logs into Align they should see the red notification at the…

Hello @Thomas A Mathews - For the dependencies between 2 programs, you need to first make sure its enabled in the "Manage dependencies" section under platform settings. Different dependency views like grid / wheel view can be used for keeping track of dependencies b/w 2 Align program, but ofcourse most important here is…

Important info The jiraalign.com domain will become available on Friday Night July 31st and will be simultaneously supported with your existing agilecraft.com domain until October 16th, at which point the agilecraft.com domain will be retired.

Lot of great insights. Thanks for sharing this.

A very helpful article Tim, thanks for sharing these insightful details.

Thanks Kent for sharing this tip about feature sync failure.