panamatriada.blogg.se - Dsync setup mapping

#Dsync setup mapping update#
#Dsync setup mapping plus#

These values can be pulled into dragonboat for future sync. If you need to have a new FixVersion, or Status, you need to create them in Jira first. Note: Dragonboat does not create new system values defined in Jira Settings, such as Status (workflow), or Assignee, or FixVersion. Tip: Ideally you may have 1 direction to avoid accidental overwrites. You can also select "Update Mapped Fields with Jira Values Now" at any point (with Admin access) to pull in fields from Jira.

#Dsync setup mapping update#

When you update any field mapping, all fields will import from Jira upon saving your changes. Here is a reference on Dragonboat data schema. The field mapping is global to all Jira projects and all ideas. If you'd like to keep selected fields in sync between Jira and Dragonboat, you need to set up field mapping and sync direction on the Jira Integration page. This mapping must be set during each individual import, this will not be an ongoing setup.

When you import EPICs from Jira to Dragonboat using JQL, you may decide which value from Jira will be pulled into Dragonboat. If you have field or project level permission for a field, the update from Dragonboat to Jira may be blocked.ġ.Fixversion, Dragonboat will pull in the 1st value in that field. If the field in Jira has multiple values, e.g.If the field in Jira is drop-down/ select, workflow status, Dragonboat can pull in new values from Jira, but will not create new value in Jira.

#Dsync setup mapping plus#

Customers on Enterprise Plus Plans can Custom Field Mapping by Project. If one or some fields are not available to the linked Jira project, the update will complete for all other fields except these fields.

The mapping is global to all Jira projects.

On-demand update by clicking the "Get Stories and Tasks" button on the Idea edit screen.

On-demand update all active ideas by clicking the "UPDATE MAPPED VALUE" link on the Integration > Field level syncing page.

Real-time update of one idea when open the Idea edit modal.

If the organization does not set up a webhook, the update from Jira to Dragonboat follows the below frequency.

If an account has enabled webhook, the changes in the mapped Jira fields will be immediately pushed from Jira to Dragonboat.

Update from Jira to Dragonboat follows 2 methods, depending on whether an organization has webhooks enabled or not. The update from Dragonboat to Jira is real-time whenever you edit an idea and Save (Save and Update Jira), the mapped fields in the Epic in Jira will be updated. How frequent is the update of mapped fields between Dragonboat and Jira? The title > Summary field is a locked/required field. Note: Mapping Dragonboat to Jira dropdown fields can help keep terms consistent rather than variable text input by users. To set up the ongoing/ recurring sync, set the mapping on the Settings > Integration page

The template set up on the Setting > Integration page is used for ongoing updates, when creating an epic, or when linking an epic.The template set up at the time of Import can be used for the 1 time or recurring import.There are 2 separate mapping templates - set up during import, and on the Integration page Set up field mapping to keep the mapped field's value in sync between Dragonboat and Jira. Each Dragonboat Idea can be mapped to one Jira EPIC, and one Dragonboat Initiative can be mapped to one Jira Initiative (using Parent Link for Jira Premium or Issue Link for Jira Standard).