Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Help us reimagine Jira Admin workflows with agents

Hi Community! đź‘‹

I’m Dmitry, a Product Manager on the Jira Admin team.

We’re exploring how AI agents can help Jira Admins automate more of their daily work and spend less time on repetitive tasks - such as Jira configuration updates, user requests related to Jira configuration, or any other time-consuming workflows.

We’re inviting Jira Admins to directly influence Jira’s roadmap, shape what an “admin agent” should (and shouldn’t) do, and help us design solutions that meaningfully reduce admin toil.

We want to understand:

  • Which admin tasks and workflows are most time-consuming or repetitive.

  • Where you’d feel comfortable letting an agent help (and where you absolutely wouldn’t).

  • How agents should fit into your existing processes, approvals, and guardrails.

  • Any insights, ideas, or examples for how you would use agentic workflows to improve efficiency.

  • Extra points if you have examples of agentic workflows you already use today for Jira Admin tasks!

What participation looks like

We’re looking for 15 Jira Admins who are open to:

  • A 45–60 minute call where we:

    • Walk through how you handle Admin workflows today.

    • Discuss where an agent could assist you with parts of that process 

    • Co‑design possible flows or agent behaviors with you.

  • (Optional) Participating in future follow-up research or early access testing.

đź“© How to participate

If you’re interested, please fill out this short form so we can schedule a call with you:

👉 Participation form

We’ll review responses and reach out via email to schedule a call soon.

 

P.S. If you have any ideas to share or discuss right away, post them below!

3 comments

Julia Foden
Contributor
March 11, 2026

My ideas where an agent might be able to help are things that I used to do in my last job by API. For example adding a long list of options to a custom field context. I didn't want to be manually copy & pasting so I would convert the list to JSON and fire it in by the API from Postman. If that could be done by an agent reading from a list in some format that would be great.

I also used to use the API to create new projects with a certain standard configuration, including adding user groups to roles and adding the new project to custom field contexts. And then I would have to manually update a load of automation rules to add the new project. Could an agent do any/all of this?

 

 

Like • # people like this
Rune Rasmussen
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
March 12, 2026

Off the top of my head, as an admin I would use agents to circumvent the current long running shortcomings of Jira/Confluence.

By far the greatest time sink in my daily work as a Jira/Confluence admin is attempting to work around missing features (that have had feature requests open for years/decades).

Also, don't you guys normally use UserInterviews for these research/interview sessions?

Like • mir_contact_stable_point_io likes this
mir_contact_stable_point_io
Atlassian Partner
May 22, 2026

Really interesting initiative 👏

One of the biggest patterns I’ve observed in large Jira environments is that admins spend a huge amount of time investigating dependencies and evaluating configuration impact before making changes.

That’s actually one of the reasons why I started building Impact Analysis for Jira.

Beyond impact analysis itself, the idea was also to explore what a real Jira Admin Assistant could look like in practice.

For example, helping admins answer questions like:

  • “What breaks if I rename this status?”

  • “What breaks if I desactivate user or remove user from group ? Automations workflow condition? Filter JQL ?”
  • “Which projects are impacted if I remove this field? Automations workflow condition”

  • “Where is this screen currently used?”

  • “What automations depend on this workflow?”

  • “Is this configuration shared across teams?”

In many cases, Jira administration becomes less about configuration itself and more about:

  • dependency investigation

  • governance analysis

  • risk evaluation

  • anomaly detection

  • understanding hidden relationships across Jira

That’s why I believe AI agents for Jira admins are especially valuable as:
âś… investigation assistants
âś… impact analysis assistants
âś… governance assistants
âś… decision-support agents

rather than fully autonomous admins making production changes directly.

That’s also the direction we started exploring with the assistant capabilities inside:
👉 https://marketplace.atlassian.com/apps/4251492671/impact-analysis-for-jira?hosting=cloud&tab=overview

Would love to participate in the research as well 🚀

Comment

Log in or Sign up to comment
TAGS
AUG Leaders

Atlassian Community Events