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
As I understand, Tasks, in Jira sits at the same level that a story sits. When integrating with Jira Align, Tasks in Jira are mapped to stories in Jira Align - i.e. Task in Jira will be created/synced as stories in Jira Align with a story type set/mapped to Task
This will ensure that the task, if updated in Jira will be synced back in Jira Align.
If we have got a bi-directional sync working between Jira & Jira Align, then in this scenario, if someone were to update the story (with the type = Task) in Jira Align, will this update be synced back from Jira Align into Jira and will the connector recognize which Task to update in Jira, even if in Jira Align it has been created as a story with the type = Task?
I would imagine it would look out for the Jira issue id to sync the updates and as soon as it finds the issue id, it wouldnt matter if it is a story or a task issue type in Jira? But wanted to get some confirmation on the above understanding?
Thanks in advance.
If you map an issue type under the "custom issue type" tab under Jira Settings, that will follow the Story workflow mapping and settings as if it were a Story.
Just as you stated, if you have an issue type in Jira, TASK, and you map it under the "custom issue type" tab, it will come into Align as a Story of Type XXX(being whatever you use within the dropdown in that setting). It will sync bidirectionally, if you have that setting enabled for Story.
I have used this many times with clients who have multiple issue types they need to sync and are at the same level as a Story.