You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Issue workflows in Jira can be quite complex. When integrating Jira with Jira Align workflows must be simplified in order to sync the Jira statuses with Jira Align states. It is recommended best practice that resolutions in Jira are also simplified to ensure that the Accepted Date of features and stories in Jira Align are syncs with the Resolution Date in Jira.
What if you need to use multiple resolutions within Jira for tracking additional metadata correlated to an issue status? By default the Jira Connector in Jira Align is configured to sync the Accepted Date for features and stories in Jira Align with the Resolution Date in Jira.
Jira Align Default Accepted Date Mapping (Admin → Jira Settings → Jira Setup → Custom Fields)
To support this mapping of Accepted Date to Resolution Date, the Resolution Date in Jira is populated by setting up a Post Function for when a story or epic (feature) issue is transitioned to the Done status (See article on Jira and Jira Align Integration: Story Resolution Transition Best Practices). In Jira, the Resolution Date is populated when ANY resolution is populated in a workflow. This limits story and epic (feature) workflows to having only one resolution which is Done that is configured as a Post Function for the final status in the workflow (typically Done).
To enable the use of multiple resolutions in a workflow, a new Date Picker custom field must be created in Jira. Below are the steps to configure a Date Picker custom field in Jira Cloud to sync with the Accepted Date in Jira Align. This solution can also be used with Jira Server or Jira Data Center but will require the use of a marketplace app such as JSU Automation for Jira Workflows that enables the creation of post-functions to update custom fields.
In Jira, navigate to Custom Fields in Jira Administration (Settings cog icon) and add a new custom field. On Select a Field Type, search for and select Date Picker (under Standard).
The Accepted Date field on the view issue screen in Jira…
…syncs with the Accepted Date in Jira Align
Jira reports and chart gadgets may not be consistent with Jira Align reports
Some Jira reports and gadgets (ex. Created vs. Resolved Issues Report) use the resolution date of issues which may be different than the Accepted Date for stories and features in Jira Align due to those two dates not being synced.
The Date Picker custom field type is an editable field
Remember that in Jira the Date Picker custom field type is an editable field which means that users can modify the date when creating or editing an issue. This can be problematic as any user can change the date which will sync with the Accepted Date in Jira Align. The solution for this is to create a new view screen with the new Date Picker custom field and associating it to the View operation for the story and epic (feature) Screen scheme (See steps 4-7). The Date Picker custom field must not be added to the screen(s) associated with the Create Issue and Edit Issue operations in the Screen scheme.
Jira issues synced with Jira Align stories as custom issue types must also use the Date Picker custom field
If Jira issues such as Bugs or custom issues are mapped to sync with the Jira Align story work item (For reference see article on Jira and Jira Align Integration: Configure Custom Issue Type Mapping and Stories of Type Defect), the View issue screen for these issue must have the Date Picker custom field and the issue workflow must also have the Post Functions added to the status transitions for populating and clearing the Date Picker custom field.