nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

🚀 Announcing the Workflow Builder Agent (Beta) in the New Jira Workflow Editor!

Rhys Christian_7so9sa

We’re excited to introduce the Workflow Builder Agent, now available as a beta inside the New Workflow editor! Whether you’re seasoned or new to Jira, this AI-powered agent is designed to make configuring and managing workflows easier, faster, and more intuitive for all admins.

Why Jira admins will love this agent

Natural Language configuration: Update your workflows by simply describing what you want in plain English. For example, “Add a transition from ‘In Review’ to ‘Done’ and restrict it to project leads.”
In-context knowledge base: Get instant answers and guidance on workflow concepts, best practices, and editor features - right where you need them.
Repetitive manual tasks: Quickly create, update, or delete statuses, transitions, and the most common workflow rules (like field validation, assignment, and restrictions) without clicking through multiple screens.

What can you do with the agent today?

WB announcement gif.gif

Q&A agent interaction for guidance and onboarding
Ask for an overview or summary of the workflow or specific configuration details
Create and edit statuses and transitions
You can currently configure the top workflow transition rules via NL:
- Update an issue field
- Restrict who can move an issue
- Validate an issue fields
- Assign issue
- Restrict transitions based on field values

How to get started

Enable Rovo on your site (required for agent access).
Navigate to the New Workflow editor via Settings (⚙️) > Work items > Workflow.
Open or create a workflow, then look for the Workflow Builder Agent in the editor.

Note: The Workflow Builder only works in the New Editor. If you are still using the Old editor, you can access the New editor from the Old workflow experience via the Switch editor dropdown.

We need your feedback!

We’re only getting started with empowering Admins and users with AI powered capabilities in Workflows and across Jira. Stay tuned for further enhancements in this space (such as Image-to-Workflow coming soon!). Let us know what capabilities would help you most!

Please try it out and give us feedback on the beta. Let us know what works, what doesn’t, and what you’d love to see next. Your feedback will directly help shape the future of workflow automation in Jira.

👉 Share your thoughts in the comments below or via the in-product feedback link!

Comments

Christos Moysiadis_e2560j

Craaaazy! Finally a way to document the workflows

Thorsten Letschert _Decadis AG_

Sounds interesting. However, trying the first conversation starter, "Can you explain this workflow" only returns something like:

I wasn't able to access the specific workflow you referenced, but I can explain how Jira workflows work in general: ...

I would expect a description of the current workflow, but Rovo does not seem to have access here. Am I missing something?

Shreeja J_th8z0r

Thanks for the update! The Workflow Builder Agent looks great - excited to try it out!

MHChang

I can't find the Workflow builder Agent,Is that expected?

Tomislav Tobijas

This is actually quite cool and can be really helpful 👀
Definitelly going to try it out in the upcoming days/weeks to see how it documents everything.

Also, if it will be able to 'bulk' update workflows based on prompt (like, add workflow properties or simply transition validators to every status/transition), that might reduce implementation time drastically.

Steven Drury

Tried this out yesterday and aside from getting pretty poor results, it seems like a solution to a problem that doesn't exist.

If you have to describe your workflows then they are too complicated to begin with, plus the status definitions are irrelevant outside of the context of the process of the project where that workflow is applied.

Dave Mathijs

Anything to get people on Rovo, right? I agree with @Steven Drury on this one.

Shelby C

I can't get the workflow builder to describe the workflow it is on nor if I give it the name of the workflow. It says some unrelated statuses and descriptions then states "If your organization has customized this workflow, there may be additional statuses (like "Waiting for Customer" or "On Hold"), but the above steps represent the standard..." okay, so.... it can only interpret the standard, non customized workflows?

Robby_uzxw2t

Another day, another pointless feature that's making my job harder.

Gary Spross

This sounds like a very helpful feature, but (as @Thorsten Letschert _Decadis AG_ & @Shelby C indicated) it doesn't seem to work for what should be the simplest ask. I understand it's in beta, but I clicked the pre-configured option "Can you explain this workflow" and the result was that it couldn't access the details of the workflow I was editing and then it provided a generic description of what a workflow is.

Screenshot 2025-08-19 112115.png

I appreciate the rollout of a new feature, but if it doesn't actually work for something straight forward like this, maybe it shouldn't have been made available yet?

Adam Taylor_yb4wyg

Hey @Steven Drury, @Shelby C, @Gary Spross, and @Thorsten Letschert _Decadis AG_

I'm Adam, a Product Manager working in the Jira team 👋

Thanks so much for taking the time to comment and share your feedback. Would any of you be interested in hopping on a zoom call with me to chat?

It seems like you've had challenges getting a good response from Rovo for explaining a workflow, and I'd love to both help but also learn from your experience in order to improve the feature.

No pressure of course, but if you're interested then please feel free to book a slot with me here 🙂

David Wuth

Trying this for the first time today. I definitely like the ease of seeing the rules for each transition, without having to open/edit them to see them.

However, I really miss being able to re-use an existing transition. That feature alone saved so much time, and made the transitions more consistent. That is a must have, IMHO.

@Adam Taylor Any chance the ability to re-use an existing transition is in the works?

Jonathan Santos

Hi @Rhys Christian

How are you? Are there more Rovo skills or pre-configured agents that can help us manage the apps? Do you have anything in mind with this in mind? Thanks

Robby_uzxw2t

After looking at this again in more detail it still lacks any appreciable value - if I was a complete novice and had never used Jira before it might help, but then I would still need to know what to ask for?

I think the issue underlying most of the negative feedback here isn't with what it does, it's what the messaging and promotion implies - this is very much a case where AI = an LLM wrapper on a probably relatively basic API into the new workflow build (which, by the way is a fantastic feature and a huge improvement). Its text-driven automation at best, as is Rovo in general - there's minimal analysis and ML going on here.

Rich Scire

When users request new workflow, I have them provide a state/transition table. For modifications to an existing workflow, I have a script that builds the state table and ask them to modify it with their changes.

What would help me the most would be to have Rovo accept these state tables and build/modify the workflow from that. Of course, it would also be very helpful to have Rovo export the workflow into a table to begin with.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-cloud

jira-administration

workflow

agent