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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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,463,421
Community Members
 
Community Events
176
Community Groups

Jira Align visibility into value steps that happen after acceptance of Features & Stories

Edited

Recently we had a customer looking to solve the problem of visualizing the entire delivery value stream for Features (Jira Epics) and Stories in Jira Align.  We explored the path of turning on the Labs feature to see 'In Delivery' and 'Delivered' states but because it's in Labs, issues found may not be supported.  Since integration to Jira will heavily rely on this working correctly 100% of the time, we opted to wait until that feature is GA'd. With that said, we have explored integrating to Jira with Jira Align Process Steps and found a few snags.  Below is the summary of the testing we did and bugs Atlassian identified in this process.  We would LOVE to hear how others are solving this problem and what paths you went down to get there.

Summary

Testing was performed on Jira Align features (Jira epics) and stories in 4 parts:

  1. Align Process Steps updated for features and stories to confirm Jira Align Lifecycle States were updated as expected (no integration with Jira).
    We did this testing to ensure the Process Step / State mapping was not an underlining issue with the Jira integration.  We did find and issue (see JAC ticket below).
  2. (Recommended Approach) Jira Status updated for features and stories to confirm Jira Align Process Flows and Lifecycle States were updated as expected.
  3. Jira Align Process Step updated for features and stories to confirm Jira Statuses were updated as expected.
    No issues found when moving forward though the process but we did find issues moving backwards after the work had been accepted (see JAC ticket below).
  4. Jira Align Lifecycle States updated for features and stories to confirm Jira Statuses were updated as expected.
    The underlining issue we found in process step - state mapping does hurt us here.  Also we had the same issue moving backwards through the lifecycle states.

The results for each part confirmed many bugs in Jira Align (all with workarounds either leveraging Jira or another option in Jira Align) with the exception of #2.  Updating your statuses in Jira when Process Steps are configured correctly, presents no unexpected behavior according to our testing in Jira Align v10.104.1. integrated with a Cloud instance.  The problem we have is that there is no way to stop an end user from updating the Process Steps in Jira Align.  If these steps are updated after acceptance on the Jira Align side, the integration doesn't work and upon the next Jira sync, it will change the Jira Align item back to the State and Process Step it was in prior to the change in Jira Align.

Bugs found

JIRAALIGN-3898 

JIRAALIGN-3705 

0 comments

Comment

Log in or Sign up to comment
TAGS

Atlassian Community Events