Skip to main content

Automate status updates from your dev tool

How to map between the Dev status and Craft.io status

Written by Maayan Ayalon

Monitoring dev progress across the items planned for release is a core part of product management. Your developers update their work in the dev tool, and you want Craft.io to reflect it without anyone updating items twice. Status mapping does exactly that.


Before you begin

You will need:

  • A bi-directional integration between Craft.io and your dev tool, set up manually or automatically by enabling the webhook

  • Your Craft.io statuses already configured. See Configuring your workflow and statuses if you have not set these up yet

  • A Pro plan or above. Dev → Craft.io status mapping is not available on lower plans. If you do not see it, reach out to your Customer Success Manager

Status mapping is not configured by default. Until you add rules, your Craft.io statuses will not reflect what is happening in your dev tool.


Status and Dev Status

Craft.io's built-in Status field covers the entire product process, from ideation and design to development and deployment. It affects your views and stats.

The Dev Status field is imported from your dev tool: Jira, Azure DevOps, or Linear. It represents only the development part of the product life cycle. For all three tools, you can also edit Dev Status directly in Craft.io. See Editing Dev Status in Craft.io below.

Status mapping connects the two. You create rules that map a Dev Status to a Craft.io Status, so the Craft.io Status updates automatically when the Dev Status changes in your dev tool.


Creating a mapping rule

Follow these steps:

  1. Open Workspace Settings → Statuses → Status Mapping

  2. Under Dev → Craft.io Status Mapping, click Add Rule. If no dev tool is connected yet, this section shows Connect Integration instead

  3. Select the dev tool status (for example, "In Review" in Jira) and the Craft.io status it should trigger (for example, "Dev in progress")

  4. Save your rule and apply changes

For example, you can set up a rule, saying that when a Jira item status is moved to “Done”, the item’s corresponding Craft.io Status is updated to “Dev Done”.


Status mapping runs one way

Rules work from your dev tool to Craft.io. When the Dev Status changes in the dev tool, the mapped Craft.io Status updates to match.

The reverse does not happen. Changing the Status of an item in Craft.io never changes the linked ticket. For example, moving an item to "Dev Done" in Craft.io leaves the Jira ticket where it is.

To update the ticket from Craft.io, edit the Dev Status field instead, as described in the next section.


Editing Dev Status in Craft.io

The Dev Status field is editable in Craft.io. When you change it, the change syncs to the linked ticket in your dev tool automatically.

This gives Product Managers ownership of the process. You decide when an item should actually move to the next status, rather than waiting for the dev tool to change first. For example, you can agree in a status review that an Epic is done and update it on the spot, without opening the ticket in another tab.

How it works depends on your dev tool:

  • Azure DevOps and Linear: open the Dev Status field on the item and pick a new value. The change syncs to the dev tool automatically

  • Jira: Craft.io respects your Jira workflow rules. It only offers statuses the item can actually move to from its current status, and prompts you for a transition reason when Jira requires one.


What comes next?

Need more guidance? 🙋 Our LIVE support team (bottom-right corner of your screen) replies to ANY question!

Did this answer your question?