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

Anyone seen bizarre Jira sync problem: Both Story and Task created for some of the Jira Stories

Edited
Samit Mehta _321 Gang_
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Feb 16, 2023

In one of my client's Jira Align / Jira integrated instance, I am seeing a bizarre issue.  I am still troubleshooting, and plan to engage Atlassian support, but wanted to see if anyone else has seen a similar issue.

My request to the community: If you've seen the following, or have troubleshooting ideas, please let me know.

Problem: For some of the Jira Stories, a Story and a Task is getting created in Jira Align. The Story and the Task both point to the same Jira issue (the Jira Story) and both their external ids are set to that same Jira Issue. Also, to make things more interesting, the Jira Align Task is parented to the Jira Align Story.

Following is a screenshot in the Team Room showing Story 61 and the child Task 30 having the same Jira Issue Key (External ID).

Anaplan - Problem with Jira Sync.png

Initial troubleshooting:

In the Connector's Jira Settings, I double-checked the ids assigned to Story and Task, and they are both different and correct.  I also checked the logs, and no errors related to this show up.  Also, the Change Log (and the Audit logs for both work items) indicates that both work items were created by the Connector (aka External System) at virtually the same time (in the Change Log, the Story creation shows up first, but is immediately followed by the Task).

Another interesting observation is that this happened to a subset of the Stories (not all Stories), and also some "normal" Tasks were created from Jira Sub-Tasks as well.

1 answer

1 accepted

1 vote
Answer accepted
Tim Keyes
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Feb 16, 2023

Its tied to logging time on a Story in JSW.  Jira Align has time logging capabilities on Tasks but not Stories.  To account for time logged on a Story in JSW the Jira Connector will create a child Task to log the time in Jira Align. 

Samit Mehta _321 Gang_
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Feb 16, 2023

Thanks, @Tim Keyes

Your response provided me the additional information needed to find the details in the following Jira Align's Help page:

https://help.jiraalign.com/hc/en-us/articles/115000088393-Jira-data-synchronization

At the end of the section on synchronization of Stories, it says:

If a story has time logged against it in Jira Software, Jira Align will automatically create a child task on the corresponding Jira Align story with the same name as the Jira story, regardless of if task synchronization has been configured. This is to support roll-up reporting of the stories.
Like Tim Keyes likes this

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events