Map field values

After you have mapped the fields, you need to map the field values for dictionary fields, such as status, priority and resolution.
Make sure that you have a corresponding value for all fields in both systems.
Usually you do not have to sync the "(null)" value from aqua. Please make sure to define a default value for your dictionaries in aqua. On the other hand it is important to map Jira null values to a dedicated value in aqua. Values with similar names are automatically mapped when creating a new sync. Even though you should check the mappings always.
Resolution is set by Jira. You need to have a mapping for all values from Jira. Additionally you need to have a value for unresolved items. We recommend adding a value in aqua, e.g. called 'Unresolved'. In Jira, items with its null value will also be shown as 'Unresolved'. Older Jira configurations handled the resolution in a special way. It could only be set in a transition screen, when the issue was set to done.
If you sync your sprint field, you need to be careful regarding the naming. Jira allows duplicate sprint names, which aqua does not allow. Make sure, that you use unique naming pattern for sprints in Jira, otherwise there can occur errors.
You can check the box to Automatically map new values during runtime. If you add a new value to a drop down field in both systems, it will automatically be mapped in the sync. Please be careful with this option, since naming must be very exact.
Using the Automatically create new values from Jira in aqua checkbox, newly added dropdown field values in Jira are automatically created in aqua at runtime if they are selected in an item to be synced. This is especially useful for dropdown lists that change frequently, such as Release, so that you do not have to maintain them in two systems.