How to map newly created statuses with Jira and Wrike integrations?
The big September update for 2022 now allows our enterprise users to customise their task statuses. This lets you add, edit and delete the statuses based on your team’s workflow. You can make these changes from the org level under “Manage Org”.
But how does this affect your Jira, Wrike and API integrations? Worry not, as we take care of it. Here’s how!
This quick video below explains everything in detail:
Map statuses to integrations
Once you access a project after adding a new status, you will see a prompt asking you to map the new status with your Jira or Wrike integrations. (You will not see this if you’ve not integrated zipBoard with either.) This step ensures that you have consistency throughout different apps.
The mapping takes place in five stages.
- You are asked to choose the project that you want to map.
- You are asked to map the zipBoard task type.
- You are asked to map your zipBoard task statuses to the integration. If you have custom statuses on Jira, this will be displayed here. This means that you can create parallel statuses.
- You are then asked to map your Jira/Wrike status to your zipBoard ones. This is necessary because the integration is now two-way. This means that if you change the status in Jira/Wrike, this will be reflected in your zipBoard project. For each Jira/Wrike status here, the zipBoard statuses available are the ones that were mapped to those Jira/Wrike statuses in the prior stage.
- Finally, a brief overview of the mapping selection is displayed. With arrows pointing in the direction of mapping.
Here's how the two-way integrations work in real-time:
Note: This feature is for zipBoard enterprise users. If you aren’t one but would like to try this feature then reach out to us at [email protected].