Sami Shaik Success Champion

Hi @Aidan Chiu , adding to what @Marc -Devoteam- and @Nikola Perisic correctly said about Guard being required, two things worth knowing before you decide on the cost: You may not need to pay per external user. Guard lets you make the default external user policy non-billable: users in it do not count toward the Guard…

Hi @Ashley_Lange , good news: I rebuilt your exact scenario in a sandbox today (Scheduled trigger, Create work item, Task under a specific Epic) and it works. The Parent field can do this, but its dropdown hides it, which is almost certainly what you are hitting. The trap: the Parent dropdown only shows "Work item /…

@Julia Foden this is exactly what I hoped people would do with the checklist: run it and post the scorecard. Thank you. Two things in yours stand out. Your site got the compact create form in May, mine still does not show it in August. That is the whole reason the audit exists: the announcement describes one rollout, but…

Thank you @Maria Reisinger _MetaFrazo_ , and consider the credit mutual: your article gave the pattern a place to land. Your runtime point is the one I keep coming back to. A rule definition you can review once, but an agent step you can only observe in what it produces, run after run. Which means the second owner you…

Excellent breakdown @Maria Reisinger _MetaFrazo_ , and the "generating logic vs understanding organizational context" line deserves to be quoted widely. To answer your discussion questions from hands-on time: yes, and the pattern that has served me best so far is narrate, not decide. Letting AI draft the rule, or letting…

@Tom Polten _RCS_ Welcome to the Community, and good news: based on everything you have verified, nothing is misconfigured on your side. As of today, Rovo not appearing in the Agent Builder app list is expected behaviour, not a fault. Here is the distinction that explains it. Atlassian's official ChatGPT integration is the…

@Brita Moorus Thank you Brita! Run the audit on your site when you get a chance, I am collecting scores in the comments 🙂

@Richard Scholtes "Never run something you didn't touch" might be the shortest usable agent governance policy anyone has written 😄 And it answers the pre-built templates question cleanly: the templates being Atlassian-authored does not make them touched, so they go through the same review as anything else before they run.…

@Darryl Lee , this is exactly the kind of cross-referencing I was hoping the comments would bring, thank you. On 7 vs 11: fair catch, and the scoping was in my head but never made it into the article. The audit covers the features an admin can verify in a ten-minute tab pass. The other four (Loom meeting updates, the work…

@__ Jimi Wikman Thank you Jimi! The comments are already improving it, which is exactly what I hoped this one would do.

Update for this thread, because the ground just moved 📰 The Jira 2026 Summer Release announcement includes Delivery Agent, a built-in agent for recurring coordination work, rolling out now and GA for everyone by the end of August. Two things about it that belong in this discussion: It arrives with the keys already in hand.…

@Becker_ Rene The social-factors point is a fair critique of every AI summary I have seen, the timeline is easy, the "why it actually took three weeks" is not 😄 Genuinely glad step 2 made the trial list. If you do run it, please come back and tell the thread what the agent's summaries get wrong first, that failure list…

@Mykenna Cepek @Troy Anderson This is an important boundary for the thread and I am glad you raised it: on HIPAA sites the whole question is moot because none of the doors exist, no Rovo, no agent actions, nothing to gate. Which is itself a governance position, arguably the strictest one available, chosen by the compliance…

@Suresh This is a genuinely valuable addition, thank you 🙏 Dedicated agent identity is exactly the missing piece the thread keeps circling: if agents act under their own accounts rather than borrowing a human's, then permission schemes, audit logs and access reviews all start telling the truth about what agents did. That…

@Becker_ Rene Fair challenge, and I will stay honest about what is idea versus experience: I have not put an agent step into a production workflow yet, these are the patterns I would trial first, in this order: Narrate, not decide. Transition to Done triggers an agent that drafts a release-note style comment from the work…

@Becker_ Rene Great question, and thank you for sharing the before/after payloads, that will save the next person real time. Here is the current state as of today, checked against the developer changelog and API docs: The new role APIs exist but are not final. The v2 Space Roles endpoints (create roles, set role…

@Kirstin Seidel-Gebert Search and chat only" is a completely legitimate answer to where the gate is, and honestly one of the most common ones right now 😄 That is the zero-doors-open position: agents can read and tell you things, but nothing fires inside a rule and nothing gets assigned. The nice property is that every step…

@zoltanersek _outpostlabs_dev_ Thank you, and apologies for the late reply, the comment reached me late. Interesting that Trigger agent action is the one that stood out to you too, it was the discovery of the whole exercise: not in the docs mapping table, just quietly there in the product. Curious about the vendor side of…

@Yatish Madhav Thank you Yatish, and apologies for the slow reply, your comment reached me late. Glad the old-to-new mapping lands, that table was the piece I most wished existed when my own muscle memory hit the new editor. And yes, Trigger agent action is the sleeper in that list. Once Rovo is enabled it quietly turns…

@Richard Scholtes This answers my blocked-vs-policied question better than I hoped 🎯 Fronting normal Rovo through your own store via MCP means the gate is architectural, not just a policy document: the path everyone actually uses runs through the layer you log and control. And your split on read-only vs write steps is the…

@Richard Scholtes I asked about three doors and you casually walked in with a fourth one you built yourself 😄 Respect. An internal AI App Store fronting everything means the logging, rights management and monitoring live in one place you control, instead of scattered across workflow config, automation governance and app…

@Brita Moorus "Co-pilot before autopilot" might be the best one-line summary of this whole thread 👏 And it maps neatly onto the three doors: the assignment door is co-pilot by nature, a human reviews every output. The workflow and automation doors are autopilot by construction, nobody reviews an agent step firing inside a…

@Chris Buzon Thank you Chris, glad it was useful. The comments are already making it better, which is the best outcome an article like this can have.

@Daniel Klein This is exactly the kind of report I was hoping the comments would surface, thank you. So we now have two live sites disagreeing: yours shows Roles central under Permissions, matching the documentation, and mine shows it under Security with no Permissions section at that level at all. Which means the honest…

@Becker_ Rene Good question, and it is really two questions, so let me split them. Are the individual permissions eventually replaced? Yes. During the transition window both models run side by side, which is the "additional feature" impression you had, and honestly the announcements leaned on that framing. But the end…

@Daniel Klein It's strange some users have it in the "Security" and some in the "Permissions".

Hi @Monica Malone The answer depends on whether your site has Jira Service Management. If you have JSM, use Surveys. They are generally available on paid plans and ship with ready-made templates: * In your service space, check Space settings > Features and turn on Surveys. * Select Surveys from the left navigation, then…

@Luke Verheyden Good follow-up, and the short answer is that reporting is not the thing to worry about here. JSM reporting counts requests, not customers. The four default reports (Workload, Satisfaction, Requests deflected, Requests resolved) are all request metrics, and custom reports are built as series over JQL…

Hello @Jens Prokoph , I tested this today in a company-managed service project, and there are three levers here, depending on what exactly you want to prevent. Lever 1: align the workflows, and the wizard stops appearing. The "Move Issue" wizard is not random: it only triggers when the work type you are changing FROM and…

Closing the loop, as promised: the removal window is now closed. The official notice held: the rollout ran 13 to 26 July through Jira's seasonal releases, and yesterday was the completion date. My own site flipped mid-window, and as of this morning the old editor is gone here with no way back. If your site somehow still…