Accepted Stories not reflected in Story Burndown chart if resolution date is missing in Jira Align

Summary

Accepted Stories with LOE points not reflected in the "Program Increment Burndown (By Story)" chart found in the "Program Increment Progress" (aka PIP) report.

Environment

Jira Align

Diagnosis

Story Burndown chart “Remaining” trend line was not decreasing even though Stories were Accepted.

(Auto-migrated image: description temporarily unavailable)

Prerequisites:

  1. PI must exist in the system and be tied to a program.

  2. Features must be created and tied to the PI.

  3. Stories, with point values, must be created and tied to features.

  4. Stories must be assigned to sprints.

  5. Stories are synchronized from Jira

If stories are not being synchronized from Jira, then this solution is not applicable.

Cause

Accepted Stories are missing the Resolution Date in Jira so it's not synced to Jira Align.

In Jira when transitioning a Story to Done, a “Resolved Date” was not set. For example, the user was required to use the Resolution screen to set the Resolution to “Done” with a Resolution explanation, but when the user does not specify a reason and interacts with the Resolution screen then it will not be marked as Resolved. Another common cause is transitioning the work to Done via API without specifying resolutiondate.

In the image below, you can see that the “Actual” Story which was marked as “DONE” has no Resolved date visible.

Since it has no Resolved Date, the Jira Connector could not send the date through to Jira Align to fill in the Accepted Date. Therefore Jira Align could not adjust the JA burndown trend line as it relies on the Accepted Date for the chart data points.

Expected: Resolved Date visible

(Auto-migrated image: description temporarily unavailable)

Actual: No Resolved Date

(Auto-migrated image: description temporarily unavailable)

ℹ️ More general info: Best practices on using the "Resolution" field

Solution

Step One:

Check the Pre-requisites

  1. PI must exist in the system and be tied to a program

  2. Features must be created and tied to the PI

  3. Stories, with point values, must be created and tied to features

  4. Stories must be assigned to sprints

  5. Stories are synchronized from Jira

Step Two:

Check the resolutiondate field of one of the Stories in Jira using the API GET command

https://your-jira-server-url/rest/api/2/issue/ABC-123

Step Three:

Check the workflow configuration of project ABC.

Project Settings > Workflows > Edit

(If you see the Workflow Diagram here, then click on Text)

(Auto-migrated image: description temporarily unavailable)

Step Four:

On Step Name Done Transitions (id) column, click Done

(Auto-migrated image: description temporarily unavailable)

Step Five:

Go to Post Functions tab and make sure "The Resolution of the issue will be set to Done" exists in the ABC workflow.

(Auto-migrated image: description temporarily unavailable)

Related Content

Updated on May 22, 2025

Still need help?

The Atlassian Community is here for you.