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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Impact of Sprint Automation Plugin in syncing sprints from Jira to Jira Align

Dear Team,

As part of our initial conversation with one of our clients, have been informed that they have a plugin - Sprint Automation (Sprint automation) on their Jira cloud instance, by virtue of which the sprints in Jira get automatically started & stopped. 

My understanding is that this should not have any impact on the syncing of sprints from Jira to Jira Align, as long as each of the teams have got their own Jira boards and for every board, the sprint automatically starts and finishes off?

Wanted to double confirm if my understanding is correct here? i.e. if the client got Jira Align implemented, the connector would still be able to sync the sprints from Jira to Jira Align?

Having a parallel conversation with the client, of course to understand why do they need a plugin like this and actually not trust their practices & the scrum masters to manage the sprints, post having a conversation with the team, rather than relying on a plugin like this.

1 answer

1 accepted

3 votes
Answer accepted
Tim Keyes
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 22, 2022

Hi @Mit Tolia

Thank you for the question.  Your understanding is correct.  The connector would still be able to sync the sprints from Jira to Jira Align.  

Pros-This could remove the margin of error making sure teams (boards) that share a Program Increment maintain the same sprint cadence so it aligns with the Jira Align anchor dates without mapping errors.

Cons-If the automation is configured with the wrong dates every single sprint mapped between Jira and Jira Align will become misaligned.  This wouldn't be that big of a deal but would take some time to clean up.


100% agree @Tim Keyes  with the pros & cons about the same.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events