Align integrates with Jira to keep the relevant work items synchronized. Align synchronizes with Jira epics, stories and sub-tasks. If you have other custom issue types in Jira, you can set up Align synchronization so those issues are brought into Align as a Story with a specific Story Type.
So if you're using Zephyr to create Test Cases, you could have the Test Case issue type brought into Align as a Story with a type of "Test Case". This might be useful if you're doing a lot of manual testing and you want to track the work being done in manual testing. If all your test cases are automated, you may not want or need to bring them into Align.
Align does not synchronize the custom fields in Zephyr that are specific to testing. (For example, Test Steps, Test Data, or Test Results.) We expect that testers will be using Zephyr in Jira for their detailed testing activities, so we don't copy those custom fields into Align.
When you create bugs in Zephyr, those can be synchronized into Align so you can track the bugs that are being fixed by developers on the team.
There's a great article in Community written by my colleague @Tim Keyes that explains how the synchronization between Align and Jira works. You can find it here: https://community.atlassian.com/t5/Jira-Align-articles/Jira-and-Jira-Align-Integration-Issue-Story-and-Epic-Management/ba-p/1259396#M59
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.