Jira Align Sync Not Updating Epic Status After Closing All Stories?

Alissa Quick

Epics in JA appear open, even though the epic in Jira shows done. After investigating I realized these epics had one or more stories still open on them which I suspect is the cause of the discrepancy. After closing or moving the open stories on the epics, I would have expected the data to resync with Align and move the epic status to Accepted. However, that is not happening. Is there a different step I need to take here? Would like to avoid manually moving epics to an Accepted status in JA.

Peter Jessen

Hi @Alissa Quick,

There are a variety of possible reasons for why you are seeing the behavior you describe.Best place to start is to look in the Audit log on the Jira epic in Jira Align. You can often determine the issue simply by reading the audit log.

Some background:

• While Jira Align will automatically change the state of a Jira epic from Not Started to In Progress as soon as the first sub-task on the first story is moved to In Progress, it will not automatically shift the Jira epic status to Accepted when all of the stories are completed.
  • This would bypass the need for a Product Owner/Product Manager to review the code against the Jira epic's acceptance criteria and definition of done.
• Jira Align will move a Jira epic (feature in Jira Align) to Accepted in Jira Align once the Jira epic is closed in Jira, assuming the connector configuration is correct.

Based on the way you describe the behavior the most likely cause is:

• The Jira workflow states are not properly mapped to Jira Align states in the Jira Align Jira Connector.
  • If other Jira epics are moving to Accepted in Jira Align when closed in Jira, then this probably isn't the reason (unless the Jira project in question uses a different Jira epic workflow than the projects that were originally mapped to Align)
  • Jira workflow state mapping allows one-to-many form Jira to Jira Align and is controlled in one set of tables in the Jira Align Admin portal.

There are several other possible reasons for the behavior you are describing. The best place to start troubleshooting is the audit log.

Feel free to post the contents of the audit log here (minus confidential info), if you can't trace the issue.

Regards,
Peter

www.linkedin.com/in/peterjessen