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
4,363,006
Community Members
 
Community Events
168
Community Groups

Jira Sprints Misalligned with JiraAlign

Edited

How to correctly align Jira Boards with JiraAlign , meaning to correctly map Future Sprints as "Future".

 

 

2 answers

1 accepted

1 vote
Answer accepted

Hi @Meena.Gundamraj1,

In order for Jira sprints to sync properly (automatically) with Jira Align sync/anchor sprints, a number of things must be set up properly:

  1. The Jira project and Jira board must be mapped to the correct Jira Align Program/ART in Jira Align via Administration -> Jira Settings.
  2. The sprints in question must be created from the Jira board of the team using the sprints.
    • NOTE: Don't share sprints between boards and don't use "bucket sprints"
  3. THERE MUST BE AN ACTIVE SPRINT ON A BOARD FOR AUTOMATIC SYNCING OF SPRINTS AND FUTURE SPRINTS BETWEEN JIRA AND JIRA ALIGN
    • This is the most common reason sprints aren't syncing between Jira and Jira Align
  4. The "Create Sprints in Jira Align from Jira" setting in Administration -> Jira Settings -> Jira Setup tab must be set to yes.
  5. The JA Program/ART must be mapped to the Planning Increment that contains the time period of the sprints in question
  6. THE SYNC/ANCHOR SPRINTS MUST EXIST ON THE PROGRAM INCREMENT OBJECT (Program -> Manage -> Show All+ Program Increments) IN JIRA ALIGN IN ORDER FOR THE JIRA SPRINTS TO HAVE SOMETHING TO SYNC TO.
    • This is the second most common reason sprints aren't syncing between Jira and Jira Align, especially if the PIs were created in advance but the sync sprints haven't been added.

Regards,
Peter

1 vote
Rae Gibbs Atlassian Team Apr 08, 2020

@Meena.Gundamraj1 If you are having issues with sprints properly mapping and are seeing errors, I highly recommend filing a Support ticket.  There are various solutions to this problem and without being able to see first hand what is going on, it is hard to recommend the correct solution.

@Meena.Gundamraj1- I certainly agree with @Rae Gibbs. If you can't resolve the issue relatively quickly using the guidance I provided, then opening a support ticket is the way to go.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events