You can sync your sprints between aqua and Jira. Using this, your items will be in the same sprints in aqua and Jira. It is necessary to create the sprints in both systems.
The sprints are mapped, like a normal dictionary field. Please be careful when naming your sprints, since all sprints that are in use must be mapped accordingly.
The sprint field is a special type of dictionary field. If you want to see, in which sprint an item is, but you do not want to sync the sprints itself, you can map the sprint field with a dictionary field.
Working with the Agile Sync
There are some things you should know, before working with a sync for sprints.
For the sync, all Jira sprints are merged together. Thus, it is important to have distinct names for all sprints in all projects, not only for the project you want to sync. Otherwise, errors may occur.
In aqua and Jira you can enter points for items in sprints. In aqua a point is always an integer. In Jira you can also use decimal numbers. Please make sure to either only enter integers, or to create a new field in Jira where only integers can be entered and map this.
Please decide how to handle closed sprints before you sync them. If a sprint is closed in Jira, you might want to deactivate it in aqua.
Syncing different issue types
You cannot only sync bugs, but also user stories, sub-tasks and what ever issue types you use in Jira. In aqua you can use defects and requirements for synchronization. Please note that you cannot use test cases. To do so, simply select the type from the drop down in the sync configurator. You can configure more than one sync for one project, in order to sync, e.g. bugs and stories. Possible issue types for synchronizing are for example the following:
• Bug
• New Feature
• Task
• Improvement
• Sub-task
• Story
Syncing User Stories
As an example for different issue types, we are going to sync Jira User Stories with aqua requirements. The first steps for the sync are the same as for a sync between defects and bugs (see
create sync). As soon as you reach the window for configuring projects, select Story from the dropdown for Jira, and Requirements for aqua.
The next steps are again equal to the usual sync.
Syncing Sub-Tasks
For syncing sub-tasks you need a new string field in aqua for the parent ID. This must be filled out manually for each new item.
The sync configurator recognizes a special Jira issue type called Sub-task. The creation of a subtask is performed after creating an existing “task” in Jira. The Sync Wizard has a different configuration for this type of issues. In order to sync sub-tasks you need to check the check box in the sync configurator.
Syncing individual issue types
It is possible to sync individual issue types. Select the item type of aqua that fits best and create the sync as usual.