Gabriela - LeanZero Community Champion

That reinstall worked because SourceTree holds onto stale credential and remote-helper state locally. Dropping in a fresh token often won't take until that local state is gone, which is why uninstalling alone didn't do it and deleting the app files plus a reinstall did. Anyone landing here still stuck should clear the…

If that screenshot is the incognito window, then a cached copy in your browser is ruled out and the entry is genuinely stuck in the space tree on Atlassian's side. The test that settles it fully is another person. Have a colleague open that same page and tell me whether San Diego still shows in the tree for them, since…

That error means Bitbucket is still getting an app password, not your token. CHANGE-3222 only fires on an app-password request, so despite switching the token over, something is still sending the old credential. The token isn't in play yet. It's a cached credential. Git and the OS hold the old app password and keep…

Markdown is the problem. Bitbucket Issues store their text as Markdown, and Jira doesn't read Markdown on import — it expects its own format (ADF through the API, or wiki markup). The raw Markdown landed as literal text, which is why the titles, code blocks and formatting flattened, and why the images came through as…

That option only shows for an Organization admin with Atlassian Guard, and your role is almost certainly the block. Provisioning for portal-only customers is set up at admin.atlassian.com, and Atlassian documents the required role as Organization admin, so a Product admin won't see "Set up provisioning" at all. SSO already…

The intermittent part is the giveaway. Bitbucket Cloud app passwords are in their deprecation brownout right now — Atlassian shuts them off in escalating windows through 27 July, then kills them entirely on 28 July 2026. Your push works between windows and fails inside them, and the deprecation warning confirms SourceTree…

Hi pankaj, the blocker before anything else is the plan. Assets isn't on Free, so there's no CMDB to load into yet — it starts at Jira Service Management Standard. Get onto Standard or higher first. After that, there's no native Snowflake connector, so it's an import job. To keep a CMDB current you'd drive it through the…

Hi Martin, the problem is the username in front of your token, not the token itself. The x-token-auth prefix you're using is only for a Bitbucket repository or workspace Access Token. If what you generated is an Atlassian API token, which is the new type now that app passwords are being retired, git wants a different…

Hi Michael, no, the Send email action can't attach a cryptographic signature. Automation hands the message to Atlassian's mail servers to send, so there's no point where you can sign it with your own S/MIME or PGP certificate. Buying a cert won't help here because the action gives you nowhere to apply it. Arkadiusz is…

Thanks for the screenshot, that changes the picture. What you're showing me is the San Diego entry hanging in the left content tree under US Server Information, which is a different beast from the embedded card I described, and that's why there was nothing for you to delete in edit mode. My earlier steps only apply when…

Hi @Mikel Whipple, you're not missing a function. The native formula field can't produce a days-since-created / aging value at all, so this isn't a syntax you can fix. `{{Created.diff(now).days.plus(1)}}` is Automation smart-value syntax; the formula field uses function calls like `DAY_DIFF(date1, date2)`, so it was never…

Hi @Veli Akiner, no, the client ID/secret you get from a service account doesn't carry the 365-day cap that API tokens do. It has no built-in expiry and stays valid until you revoke or rotate it. The short-lived piece is the access token you mint from it: POST grant_type=client_credentials to…

Hi @Sweta Shah, first thing to rule out is the menu itself. Around March 2023 manual rules were moved out of the old Automation list and into the Actions dropdown next to the Status button on the issue, the same place looped workflow transitions appear. Open that on your test issue first. If it's still not showing, open…

Ah, that changes it. The built-in Field Required validator fires on every run of that transition, so there's no native setting to have it only kick in when the SDLC Exempt checkbox is empty. Native conditions and validators can't read the value of a custom checkbox to decide whether to run. To get the conditional part…

The per-issue-type part carries over into a single scheme, so you don't need 25 to keep it. In Field Schemes the work-type differences sit on the scheme itself as per-field overrides keyed by work type, so a field can be required on Bug, optional on Story, hidden on Task, all inside one scheme. That's the same behaviour…

Good you checked the hierarchy that closely. You're right that your setup doesn't match the cause in that KB, so scratch the bit about Initiative sitting at the Epic level. The thing that changes the picture is what the template reaches for when it provisions. It only goes one level up from Epic, so it uses whatever work…

Hi @Wil Jones, Arkadiusz and Gor are right that it's a current limitation, and AX-1938 is the ticket that maps to it exactly. The Rovo search scopes (`search:rovo:mcp` is the one you flagged) aren't offered when an admin generates a service-account API key right now, so you're not missing a step in the console. Per that…

Hi @Julian Becher, that Agents section isn't a field on the layout, so there's nothing to hide under Project settings or the work-type config, which is why you came up empty looking for a toggle. It ships with Rovo and Atlassian only exposes it at the Rovo level, not per project or work type. The only way to take it off…

Those two are all the action exposes today, but the page id and space key are both in the URL already, so you can get them now without waiting on the feature request. `{{createdPage.url}}` comes back as `.../wiki/spaces/SPACEKEY/pages/PAGEID/Title`. The page id is `{{createdPage.url.substringBetween("/pages/","/")}}` and…

Hi Misha, this looks like a regression on Atlassian's side, not anything you changed. The docs put the ceiling for custom pipeline variables at 350 variables and 512 KB combined, with 120,000 characters per value (https://support.atlassian.com/bitbucket-cloud/docs/variables-and-secrets/). The 50 count and 10,240 bytes…

Hi @Sanuthma Sandanaki Munasinghe, yes you can. The Text Field (read only) type just controls whether users can edit the field on the screen. The value itself can still be set programmatically. Your API call failed because the field isn't on the edit screen, so add it to that issue type's Edit screen. It will still show as…

Ajay's right that the other templates working rules out a plan or permission problem. The extra detail I'd add is that this one has a known cause. The Top-level planning template is the only one that provisions above the Epic level, so it leans on your work type hierarchy in a way the standard templates don't. If there's…

Hi @Yawen, welcome to the community. That exclusion rule from Advanced Roadmaps is still in native Plans, just renamed, which is why searching for "Exclusion rules" came up empty. It's now the Removed work items tab. Next to your plan's name in the sidebar, open More actions (•••) → Plan settings → Work in your plan →…

Since you already archived them, that's the snag - an archived project can't be deleted straight off, you have to restore it first and then send it to trash. To get it back, go to the gear icon (Settings) top right, then Projects (some sites now show this as Spaces), pick Archive in the left sidebar, find the project and…

That option is missing because 4.1.9 is too old. Atlassian added the API Token auth type in the 4.2 line, and the docs say to be on at least 4.2.14 on Mac. On 4.1.9 the dropdown only ever shows Basic and OAuth, which matches what you're seeing. So first, Sourcetree menu > Check for Updates and let it pull the latest. Once…

Jason has the core of it. The reminder email goes to the person who created the token, and only to them. The gap that bit you is on the admin side. There's no org-level alert or inventory that tells an admin some token in the org is about to lapse, so if the owner isn't watching their own inbox it slips straight past,…

Yeah, if your backend expects an Atlassian 3LO access token then Basic auth is off the table without touching your auth model, so external store it is. Two things that bit me when I wired this up. The rotation is single-use — the moment you refresh, the old refresh token is dead and you get a new one valid for another 90…

Good news is the id is right - the number in the page URL (1063944234) is the page id the v2 endpoint wants, so you're reading that off the URL correctly. The 404 is the misleading part here. Confluence returns a 404 on that endpoint in two very different cases - either the page genuinely doesn't exist under the cloudId…

The database itself and the card that displays it on the page are two separate objects, and that's the whole reason for what you're seeing. When you delete the database it goes to the space Trash, but that action doesn't edit the page, so the page still holds the embedded database card. And while the database is only…

Hi @Gustavo Pfeifer Meijer, that error comes from the projects your features belong to. When you drag a feature to change its rank, Plans writes the Rank field back onto each work item in Jira, and Jira only lets you set Rank if you hold the Schedule work item permission (together with Edit work item) on that project.…