Gabriela - LeanZero Community Champion

Hi @Alec Nikolov, that @JIRA in Slack is the Rovo-powered agent, and the error you're getting is about the Jira site behind that mention. The Slack connection you added is a separate piece. Rovo has to be active on that site first. Atlassian's requirement is that an organization administrator activates Rovo in Atlassian…

Hi Santo, open one of those requests and look at the raw source of the original email. If the From header reads something like "Sender Name" via GroupName followed by your support address, that's what you're chasing, and it isn't really a Jira setting. The DMARC policy you just published is the trigger. Forwarding to your…

Hi @Serigne, on your first question, no, not natively. The HTML email parsing setting you already switched on only picks between wiki markup and plain text, and that is its full documented range. Which project type are you on? That page documents company-managed only, so if you're team-managed the Space settings path Arek…

Hi @Emma Handley, you don't need an app to read status back at a date. Viswanathan's JQL is the one to run, though the date window in it will cost you a day. project = ABC AND created >= "2026/04/01" AND created < "2026/07/01" AND status WAS "In Progress" ON "2026/06/30" A date with no time component is read as midnight,…

Hi @Lena Wong, known limitation, and attempt 1 is where it shows. Filter to issuetype = Epic and the hierarchy stops rendering, which is JRACLOUD-94328, Gathering Interest, 29 votes. Attempt 2 gets the arrows back by pulling every child into scope, so each child then takes a root row of its own. Same reason Collapse all…

Hi @Casey Gould, the toggle is real, but Atlassian publishes two routes to it and I gave you the one your admin UI isn't showing. The other runs Atlassian Administration, then Rovo, then Rovo access, Sites tab, expand your site, then Manage under More actions on the connector row. Slack and Google Drive both reach search…

Carmine, one thing I got wrong. I sent you to the board workload for once the sprint starts, and on a company-managed board those same numbers are already on the sprint in the backlog, while you're still planning it. Look for the assignee avatars at the top of each sprint. More actions next to them opens Workload by…

Hi @Prabakaran Prabu, in your first screenshot the warning comes from Rovo itself and lands after the Review and submit card, so the agent side is fine and it's the create call getting refused. Was that a DM or a channel? Rovo runs on your own permissions in a DM and on the bot account's in a channel. Your second problem…

Not today, going by anything Atlassian documents. Every documented way of attaching a Microsoft mailbox on Cloud runs through an interactive sign-in, and the tell is what happens when the wrong person does it. Their KB on that admin approval error warns that authenticating with an Azure AD admin account adds the admin…

Two documented things switch that option off, and it's worth ruling both out before you write it off entirely. Sprints first. Atlassian's team-managed doc says it flatly, if you have the Sprints feature enabled you won't be able to manually clear work items from your board. Second one is permissions, only space admins and…

For the endpoint: claude mcp list prints each server with its URL right on the line, so you'll see what the Atlassian one actually points at. claude mcp get atlassian gives you the full definition, or it's the url field in ~/.claude.json. Your server-side read is right, and it isn't the endpoint or the plugin version. It's…

The 25-section prompt is the root of it. One agent with a long rulebook stays probabilistic. Each extra forbidden-phrase line adds noise without adding control, and the wrong-order and duplicate-call symptoms are what an overloaded agent does. Split it. Rovo has native subagents now (the feature that used to be called…

Field value changed on Team won't catch a move-in. Your instinct was right. That trigger only listens on create, edit, transition or assign, a move is none of those, and a ticket that lands blank and stays blank hasn't changed Team anyway, so there's nothing there for it to react to. The Work item moved trigger you floated…

Those two lines are OAuth scopes on the grant, so the fix lives on the auth side. Create and update pages is write:page:confluence, Create and update comments is write:comment:confluence, and your token came back without them. Worth ruling out a Confluence space permission too, but the wording you quoted is the…

The counting works the way you said, which undoes my warning. A run only counts when it performs an action. Atlassian's usage page puts it plainly: if a flow runs but doesn't successfully perform an action, it won't count toward your monthly usage, and there's a worked example there with a trigger, a failing condition, and…

Two different auth planes, and that's the whole of it. Calls to your site host take basic auth with your email plus a personal API token, which is why group/bulk works for you. Point that same token at api.atlassian.com/admin and it dies both ways: basic gives you 401, bearer gives you 401. That host wants an Admin API…

In a Comment on work item action, [~accountid:{{issue.reporter.accountId}}] renders as a real mention. Atlassian's own example uses the assignee, same shape. Two traps sit next to it. Skip {{initiator}}. That's whoever triggered the rule, so on a scheduled no-reply rule it lands on your automation user. Wrong person. The…

Poking, since you asked. The logic is fine. The trigger is where it bites. Work item updated fires on every edit of every ticket in the project, so that rule runs constantly. Automation runs all come out of one pool per product, and single-project rules stopped being exempt from it back in 2023. What should worry you is…

Correction on my opening line, because your own evidence beats it. I counted the picker on a current Cloud site while writing that. Thirteen types in the top group: Checkboxes, Date Picker, Date Time Picker, Labels, Number Field, Paragraph (supports rich text), Radio Buttons, the three Select Lists, Short text (plain text…

Nothing is rolling out and it isn't the trial. What you're looking at is already the full list. The curated-shortlist-with-an-All-toggle behaviour is real. It's a Data Center thing. Server's dialog opens on a standard set and makes you pick All to see the rest. Cloud's doesn't work that way. The whole set renders in one…

Standard covers three of your four. Worth knowing which one it doesn't. For what everyone's working on, stop thinking per project and build a board off a saved filter instead: Boards, Create board, Board from an existing Saved Filter, with JQL spanning whatever slice of the 15 you want in one view. The same filter drives…

Good catch on the endpoint, Arek. It's scoped to the global Labels field, so any Labels-type custom field someone's added is invisible to it, and an audit built on it alone would quietly under-report. To cover those you'd pull the field list first, keep the ones whose type is labels, then query each by id rather than by…

Your second guess is the right one. The kibsa.at address is your Atlassian account, and that's what belongs in User Email. The other one isn't an account at all. That's the bit tripping you up. In a remote like https://name@bitbucket.org/workspace/repo.git you're looking at git's own user@host syntax, where the part before…

Your no-access half is still open, and it's the easy bit. A rule runs as its actor, not as whoever tripped the trigger. So point the actor at an account with rights in the target space: the clone lands there fine while your agent still can't see the project. It's set in the rule's own details. That's also why automation…

There's no list to find, because a label isn't an object Jira keeps on its own. It exists only through the issues carrying it. Atlassian's KB puts it plainly: to delete a label you remove it from all the issues where it's used, and once it's gone from all of them it stops showing up when you browse. No admin screen, no…

That error is coming from SourceTree's account check, not from git. It calls api.bitbucket.org/2.0/user to read your profile, and that call wants your Atlassian account email as the username. Git wants x-bitbucket-api-token-auth instead, which is why the same token sails through the URL method while the Accounts tab keeps…

Those types were renamed, so it's probably less broken than it looks. In the current create-field screen, Text field (single line) shows as "Short text", the multi-line one as "Paragraph", and Date Picker as "Date". That's straight from Atlassian's own field-types list. None of them are plan-gated either, so a Free trial…

Plans has an over-capacity signal natively, so try this before reaching for an add-on. Set each team's capacity in the plan, in story points or hours. Then every sprint on the timeline shows a bar that fills as you assign work and turns red once that sprint goes over. That red bar is your realistic-or-not check, built in.…

Jira's own answer to most of that list is Plans (it was called Advanced Roadmaps). One timeline across many projects, capacity per team, dependency lines between items, and it reads from your existing boards, projects or filters rather than holding a second copy of the data. The catch is the tier. Plans only opens on…

There's no separate git uninstaller to hunt down, and that's the clue itself. The embedded git isn't a Windows program, it's a folder inside SourceTree's app data, which is why git on the command line finds nothing and why the config came back empty. Nothing to uninstall, you delete the folder and it's gone. For a clean…