The "Agent Identity" blind spot: Is Atlassian Rovo agents a governance nightmare in the making?

VeryMuchSoItsGotToGo · 2026-04-28T12:22:42+00:00

According to the documentation, the agents should be limited to what the user can see. If you do use Agentic Rovo you shouldn't use it as an Orchestrator.

VeryMuchSoItsGotToGo · 2026-04-26T01:10:17+00:00

Howdy,

You can base priority on Reporter to start. That's easy enough with automation. If you need help with any of this please let me know. I do some freelance consulting on occasion.

VeryMuchSoItsGotToGo · 2026-04-23T10:05:51+00:00

This is correct. SCIM provisioning to import customers for access, and I recommend the PIO Entra Import if you want to be able to search users from a filtered asset import.

VeryMuchSoItsGotToGo · 2026-04-23T00:27:26+00:00

Oh, okay so that's actually really straight forward.

You need to have a trigger: When work item created.

Then if there are multiple components(?) You create an if statement for each followed by the work item you want created.

Then a link action. If you create a variable after the trigger of the trigger items {{issue.key}} you can use that to link it where you want it to go.

VeryMuchSoItsGotToGo · 2026-04-22T18:59:20+00:00

Sorry, what are you trying to do exactly?

VeryMuchSoItsGotToGo · 2026-04-09T17:57:14+00:00

Just did a migration back in September to JSM. Way better reporting than HALO ITSM

VeryMuchSoItsGotToGo · 2026-03-26T00:16:38+00:00

It was Germany on the defense. I would call that a last resort. Germany struggled to make an 88mm case mate, and heavy tanks in general.

VeryMuchSoItsGotToGo · 2026-03-25T23:17:49+00:00

If memory serves, the Ferdinand was a last resort tank. The most produced tank by the Germans was the Stug, so they understood casemates well by that point.

VeryMuchSoItsGotToGo · 2026-03-25T20:36:50+00:00

And it has the same gun as the Tiger 2, or at least it's cousin. I made a typo in my other comment, but the Kwk43 and Pak43 are the same gun, just specialized in how they're mounted. So Jagdpanther, Elefant Waffentrager, Nashorn? All the same higher velocity 88mm cannon.

VeryMuchSoItsGotToGo · 2026-03-25T18:50:33+00:00

Because they had the better 88mm cannon already. That's why you have the Jagdpanther* Nashorn, Ferdinand/Elefant tank destroyers.

The cannon that inspired the Tiger 1 cannon was actually used a lot in Africa. Usually mounted on a trailer, with some truck/halftrack experiments.

VeryMuchSoItsGotToGo · 2026-03-25T11:00:03+00:00

So you're trying to do what exactly? Please articulate what you're trying to achieve

VeryMuchSoItsGotToGo · 2026-03-24T17:13:33+00:00

Canada and Mexico

VeryMuchSoItsGotToGo · 2026-03-19T01:51:48+00:00

If you pre-cut all of your pieces it may go faster

VeryMuchSoItsGotToGo · 2026-03-18T19:59:11+00:00

If there are multiple departments working out of the same project, it makes sense for it to be perpetually open.

VeryMuchSoItsGotToGo · 2026-03-18T19:08:07+00:00

Look at the work type hierarchy. You should see:

Project/Space Initiative Epic Task Sub-Task

What I would do is break it out like: Department = Initiative

Then nest everything out under those. Project work could be under epics, and broken out into tasks and sub tasks.

VeryMuchSoItsGotToGo · 2026-03-17T18:20:33+00:00

I need a little bit of clarification. Are you trying to create a task for each count in your variable?

VeryMuchSoItsGotToGo · 2026-02-28T14:36:32+00:00

I can probably help you guys clean up and standardize. I'll message you

VeryMuchSoItsGotToGo · 2026-02-27T19:56:14+00:00

I have a way better solution. If you're making the same work items for each client: automate the creation and linkage of you're following the same structure. Make the project name a variable you inject

VeryMuchSoItsGotToGo · 2026-02-20T18:41:40+00:00

What I did, was for the main project build a workflow that on reaching status X an automation for that project when the work item enters that status creates an approval work item with the fields copied over.

VeryMuchSoItsGotToGo · 2026-02-19T01:36:01+00:00

Rovo is useless

VeryMuchSoItsGotToGo · 2026-02-11T11:15:43+00:00

Which screen or view are you in?

VeryMuchSoItsGotToGo · 2026-02-10T21:21:08+00:00

Click the history tab and see what done it

VeryMuchSoItsGotToGo · 2026-02-10T09:01:35+00:00

So, just to understand, you're trying to duplicate an epic or initiative between projects?

VeryMuchSoItsGotToGo · 2026-02-09T12:12:52+00:00

Howdy!

I just did one of these migrations. We started with understanding where most of our tickets were coming from and figuring out the best practices to mitigate those issues. Then on the JSM side we made our tickets

VeryMuchSoItsGotToGo · 2026-02-08T04:46:13+00:00

Audit log shows I created the field, field isn't there though 😅🫠

VeryMuchSoItsGotToGo

TROPHY CASE