Until now, Dev Status was a one-way mirror. It synced from Jira, ADO, or Linear into Craft.io, but any change had to be made on the dev tool's side first.

Product teams reviewing progress in Craft.io during planning or status meetings had to break out of the conversation, open the linked ticket, make the change there, and come back, extra steps that discouraged teams from treating Craft.io as their source of truth for status.

Now the Dev Status field is editable right where you're already working. For items synced with ADO or Linear, just open the field and pick a new value, it syncs to the dev tool automatically.

For Jira, Craft.io respects your workflow rules: it only offers statuses your item can actually move to from its current state, and prompts for a transition reason when Jira requires one. This means you can run an entire status review inside Craft.io, agree an epic is done, update it on the spot, and trust it lands correctly on the Jira, ADO, or Linear side, without a single tab switch.
​