Gabriela - LeanZero Community Champion

Hi @instrumentally, your screenshot shows the left nav already sitting on Security, Data contribution, so the route isn't the problem here. The role probably is. Your post is tagged Product admin, and the only role Atlassian documents for that setting is Organization admin, stated at the top of the Include or exclude…

I was wrong to walk that back, so back it goes. The line I quoted first is in the article itself, under Update as of 30 Jul: we are still evaluating the possibility of bringing back manually clearing done items however not in its current state. When I went to check it I re-read only Peter Oh's comment, where the same thing…

Going back to the manual clear, I paraphrased Peter Oh's update more optimistically than it actually reads. His words are that removing it was a conscious decision, that the feature in its current state was confusing for many customers, and that they may explore bringing it back in future. A maybe, some day. So don't plan…

Hi @Dermot Tiernan, the residency pin and the AI training opt-out are two different switches. The second one is in Atlassian Administration, then Security, then Data contribution, and Atlassian starts using data according to whatever it says there on 17 August 2026. Your post is tagged Standard. The default follows the…

The Single User claim I made doesn't hold up. I leaned on an old thread and stopped reading it too early. It's Jira Server 7.2, not Cloud, and the person investigating there tried twice, on 7.2.0 and on 7.9.2, to reproduce a Single User recipient getting mail through notifyUsers=false, and couldn't either time. The…

The reviewer list is a separate bug. Reviewer search only stays scoped to your workspace when the repository is private, on a public repo it searches every Bitbucket account, which is how someone from User2's workspace, and maybe your old colleague, surfaces as a suggestion. Check Repository settings, Repository details,…

Hi @Lindsay Anthony, the Hide unused fields toggle doesn't fit here - that one hides fields per user in the UI. Your getCreateIssueMetadata check shows the fields missing from the API response itself. Different animal entirely. This lands in the class where forum troubleshooting usually stalls, because the actual…

Hi @Stefan Tolksdorf-Cyron, if those Issue Commented recipients are set up as Single User entries instead of a role, group, or Watcher, notifyUsers=false skips them regardless of the caller's permissions. That part isn't scope-fixable. Someone hit exactly this before - full Jira-admin rights, still got the mail, and…

Hi @Sunil_Bhadauriya, the panel doesn't show it but the work item does record it, and not only through the API. The Workaround section on JRACLOUD-76004 is Atlassian's own, check the issue's History tab to see who uploaded the attachment. That one has sat at Gathering Interest since February 2021, 146 votes and 67…

Hi @Alexander, the User Workload Report is the closest built-in one, and it stops short of utilization. Atlassian's own wording is the ceiling, the number of unresolved work items assigned to the specified user and the remaining workload, per space. Allocated work. Nothing to hold it against. Plans won't close that either,…

Hi @Rachna Bhavsar, this is the same one you raised as Unable to see other users' branches when creating Pull Requests, and Ben from Bitbucket Cloud Support has already taken that thread and has your two trace IDs. Keep the rest of it on that thread. The ex-colleague still showing in the picker is worth him having, and…

The 1 day option is a board View setting, so it doesn't reach the Backlog. The Backlog screen carries its own View settings and it's a different list, version panel, epic panel, quick filters, density, fields, swimlanes, card layout. Nothing there for done items. Different team as well, which is what explains the split. On…

I need to walk back the second half of that. The Trust Center advisories page only carries Data Center and Server advisories, and your post is tagged cloud, so nothing for your site will ever land there. Wrong pointer from me. There's no feature, and Atlassian says so on its own page. It asks "Is there a Security Bulletin…

Correction to my earlier reply. I built that ARI from the wrong field. ari:cloud:jira::site/{guid} is the example the spec hangs on the role association resource, and that field's own description contradicts its example. It lists which resources are valid and jira is not one of them. jira-core, jira-software,…

Hi @WP , true. The request to choose the colour yourself is JRACLOUD-40855, opened in 2014, still Gathering Interest, 280 votes, no resolution, and its entire description is one line, I think it would be a nice feature to set a color to a label. The Server and DC twin JRASERVER-40855 sits in the same place. Twelve years at…

That 404 is the visibility gate, not the flag. You swapped scope sets and the error didn't move, which fits, the endpoint returns 401 when the credentials are incorrect or missing and 404 when the issue is not found or the user does not have permission to view it. Edit issue asks for Browse projects and Edit issues on the…

Hi @Blaine Blodgette, it exists, it lives outside the product. Atlassian's advisory publishing policy commits to posting each advisory on the Trust Center page at the same time as the fix ships, and critical ones also go to the Alerts mailing list for that product. You opt in at my.atlassian.com/email under Tech Alerts.…

Hi @4001 126, the GUID is the site id, so Trudy's links get you that part. What neither of those covers is that a resource is a product on a site, so one site hands you a different resource id for Jira and for Confluence. The shape is ari:cloud:{product}::site/{siteId}. Note the empty segment between the two colons.…

Yes, and I can drop the hedge I put on it. Atlassian documents that exact route as the workaround on JRACLOUD-97682, "Add notifyUsers=false option to comments API", raised 4 March, still Gathering Interest. The Workaround section on the ticket is a PUT to /rest/api/3/issue/ABC-1?notifyUsers=false carrying…

Hi @Stefan Tolksdorf-Cyron, sendNotifications isn't a parameter of that action, so nothing evaluates it. Your export proves it's stored, your inbox proves it isn't read. The action exposes the comment body and its visibility, which is why publicComment survived and changed nothing. The asymmetry you found is documented in…

The rollout article got an update today, dated 30 Jul. One day is an option for hiding done items now, alongside 7, 14, 30, 60 and Never. That's as close to removing them now as the current board gets, and it takes @Anders Dahl's 7 day filter down to one. Same update speaks to the manual clear. That's the thing I couldn't…

Hi @colleen_brondou, it's gone deliberately, and Atlassian commented on whether it comes back in an update today. This is the board rollout for team-managed Software spaces, Kanban side of it, so it only applies if that's the space type you're in. Company-managed boards aren't part of it. The timed clearing moved into View…

Correction to what I posted here on the 20th. I sent you after a control that isn't on your board, and your screenshot had already said so. Trudy had it right. What I quoted was the team-managed getting started doc, and it still describes the old board, 14 day auto clear and the manual clear both. So treat its sprints and…

Viswanathan, the agent-interface scopes are real but they belong to the preview endpoint, mcp.atlassian.com/v1/mcp/preview. That same page's troubleshooting says a scope error is what you get from GA scopes against preview or the reverse, so adding read:confluence:agent-interface to a GA token won't move this one. Same for…

Hi @Emma Phillips, for the Atlassian side of this the grant should come out as a group membership in Entra and nothing else. Once user provisioning is connected, your users and groups sync into the organization and product access is granted off those groups, so an approval doesn't have to end with someone opening…

Hi @Mina Sultan, there's no AQL field anywhere in the chart builder. A chart is a metric, a group-by, an optional segment and up to five filters, and all of those work on attributes of the object type you are charting. Department sits two references away from PCs, so nothing in that config reaches it. Atlassian's own…

accountStatus isn't reporting site membership. Atlassian defines it as the lifecycle status of the Atlassian account itself, three values, active, inactive and closed. An invited person who hasn't accepted yet still has a perfectly good account, so it reads active. Inert for what you want. On my own site it comes back…

Hi @Devika Sahadevan, no on the first one, and ACCESS-2077 is where Atlassian says so. The request is asking for exactly the split you want, in its own words: a more granular option that restricts saving and backing up to external devices or the cloud while still allowing users to copy links to issues. It also records that…

Hi @Aslak Niclasen, there's no scope left to add. Atlassian's supported-tools table gives getPagesInConfluenceSpace the same requirement as getConfluencePage, read:page:confluence, and that call returns 200 for you, so the scope is on the token and the gateway is accepting it. The 401 is that one tool asking for something…

@stefan_lutter that consent screen is fixed. Atlassian closed issue 204 on Monday, write_confluence is being offered again and the four write tools come back once you authorise. Which flips what I told you about the colleagues who still had write. Reconnect them. A grant issued while the bug was live doesn't inherit the…