Gabriela - LeanZero Community Champion

That leftover-config thing is the actual root of it, and you don't have to hunt for the files by hand. Git will name them for you. Run this in a repo: git config --show-origin --get-all credential.helper Each line comes back prefixed with the exact file it's read from, something like file:C:/Users/you/.gitconfig or a path…

That's exactly it. Git over HTTPS asks a git credential helper for credentials, not SourceTree, and on Windows that helper is the Git Credential Manager. So even with SourceTree emptied and no Windows Credential Manager entry, git's own helper config still kicks in and hands over whatever it has cached, which is why a pull…

The reason you can't create a ticket against the cloud project on jira.atlassian.com is that it isn't a support channel. That site is Atlassian's public bug tracker, where you can watch and comment on JRACLOUD bugs like the two you found, but not open your own support request. Commenting "this is recurring" adds a…

The native tool for exactly this is the Page Properties macro, paired with the Page Properties Report. It's a step up from a loose table at the top of the page. On the template, add the macro and put a two-column table inside it: the left column is the attribute name (Document ID, Effective Date, Owner, Review frequency),…

Ah, that one's on me. I gave you the REST-API username by mistake. Your email is what you'd use for REST calls, but for a git push or fetch the username isn't your email at all. It's x-bitbucket-api-token-auth (or your exact Bitbucket username), with the token as the password. That's why it kept bouncing you: git was…

Not officially. Atlassian supports SQL Server authentication (the DB username/password you're on now), and Integrated/Windows Authentication for the database connection sits outside their support scope, so they won't back you if it misbehaves. That's the caveat. That said, it does work and Atlassian has KB articles for it.…

For git push/pull, only the git:https://... entries matter. The hg: ones are Mercurial, ignore those, and the sourcetree-rest: ones are SourceTree's own account API rather than your git auth. Of the three git: entries, the one git falls back to is git:https://bitbucket.org, the host-only one with no user in it. Your…

Company-managed Jira has no native way to show a field on the edit screen but stop people editing it. A field is either on the edit screen (editable) or not there at all. So visible-but-locked isn't something the screen config alone can do. The clean way is ScriptRunner Behaviours, or a similar behaviours app like JMWE.…

Turns out you don't need to configure anything. This is a known Jira quirk, not your setup. The assignee picker on a board card and the one inside the issue detail are two different code paths on different user-search backends, so the card one can come up empty (only Unassigned and Automatic) while the detail one finds…

Yeah, OAuth still works with SourceTree, and it's not on the chopping block like app passwords are. Might actually be your easiest way out of this whole mess. Drop the Bitbucket account you've been fighting (Tools > Options > Authentication), then Add Account again and pick OAuth for the auth type (not Basic or API Token).…

The Set to recur shortcut James pointed at is the cleaner path, and I was too absolute yesterday saying JSM has nothing native. It does work on JSM Cloud. Worth flagging for Mark though, since maintenance usually runs monthly or quarterly: the Set to recur quick-pick only offers daily, weekly, and fortnightly. You won't…

The clean way to know is the date itself. App passwords get switched off entirely on 28 July, so if your pushes still work past that, it's the token. Nothing else survives that cutoff. Right now you're mid-brownout, so a push working today isn't proof. To check before then, open Windows Credential Manager and find the…

JSM doesn't have a native recurring-ticket feature, so the way people handle this is a scheduled automation rule. One rule per cadence. Go to Project settings > Automation > Create rule, pick the Scheduled trigger, and set how often it fires. There's a simple rate ("every 4 weeks") or a cron expression if you need…

Quick filters only change which cards show on the board, not who appears in the assignee list, so that one's a red herring. And it's very likely not a Browse Users permission gap either. If it were, the side panel wouldn't find Cason for you, and it does. So the lookup itself works. The board's inline picker is behaving…

The board only treats the LAST column as done. That's the whole thing here. When you added RELEASED to the right of DONE, DONE stopped being the final column, so the board no longer counts it as complete, which is why it went blue. A board has exactly one completion point, the rightmost column, which is why you can stack…

Before I send you chasing another fix, let me back up, since I've been guessing at your setup. Are you on Confluence Cloud or Data Center? And on the task in your screenshot, is your name set as the actual assignee on it, or is it only @mentioned in the text? That distinction is usually where this hides. A task shows under…

x-token-auth is actually right for the repository token you made. It'd only be the wrong username if you'd generated an Atlassian API token instead, which you didn't. So that part's fine. Most often that "you may not have access" error on an otherwise-valid token is the scope. A repository Access Token created without the…

That padlock means it's a locked field. Whatever created it told Jira not to let anyone reconfigure it, so the usual path to add options (Issues > Custom fields > your field > Contexts and default value > Edit options) is greyed out or missing entirely. Depends what owns it. If a Marketplace app created the field, that app…

That confirms it, and it comes down to what the rule treats as the "current" issue. Your trigger is the Epic, so the Epic stays the in-scope issue for the whole rule. When you link the MONITORING task, the Link work items action is really linking the in-scope issue (the Epic) to MONITORINGkey — which is the pairing you…

Don't name the variable createdIssue — that clashes with the built-in {{createdIssue}} smart value, so referencing {{createdIssue}} downstream gets ambiguous. Rename it to something unique like task2Key, and reference {{task2Key}} in the link step. The bigger thing is usually the Link work items action itself: it links…

Yes to the creation part, and it fits in one rule. Add a Create work item action for each issue — task1 in project1, task2 in project2, story1 in project3, the three subtasks under story1, story2 in project4. The one gotcha: {{createdIssue}} points at the LAST thing you created, so right after each Create, add a Create…

The anonymous-access setting only covers people who aren't logged into any Atlassian account. Someone signed into a different Atlassian Cloud site is authenticated, so the portal doesn't treat them as anonymous — it checks whether they're a customer of your help center, and since they aren't one of your org's customers,…

Jason's testing is the accurate picture, and I owe you both a correction — the HTML export doesn't rebuild the tree as folders. The page files come out flat in one folder, and the hierarchy only survives as the links inside the HTML (the index.html ties them together in order). Attachments do get split by page, under…

@Gene Parilov here's a script that'll do the run. Rather than fix the mangled issues in place, it goes back to Bitbucket, reads each issue as its original Markdown while Issues still exists, converts that to Jira's format, and creates a clean issue. The images get pulled from Bitbucket and re-uploaded as attachments on the…

It's doable natively — the space export is what you're after. Next to the space name, More actions (•••) → Space settings → General → Export space, then choose HTML. You get a zip of the whole space with the page tree intact, and each page's attachments come down in their own folder named by the page ID, so both the…

That on/off pattern isn't random — it's the brownout schedule. Atlassian is retiring Bitbucket app passwords (CHANGE-3222) with scheduled windows at 00:00, 06:00, 12:00 and 18:00 UTC, and this week they're running about 3 hours each. Inside a window, anything still authenticating with an app password fails with that…

That error only fires when an app password is actually being sent. So despite SourceTree showing OAuth connected, git is still reaching for a cached app password on the pushes that fail, which is why it's intermittent. SourceTree's account auth and what git actually hands the remote on a push can be two different…

@Arkadiusz Wroblewski — the point that it depends on the integration is fair, and I've reworked the answer around it below. The "hallucination" call isn't, though. The egress ranges, the direction field and the change-notification topic are all straight out of Atlassian's own docs, not invented — the answer was too general…

Rovo's callbacks leave Atlassian cloud through the same egress proxies every Atlassian cloud product uses, so there's no Rovo-specific IP list to allowlist. What you want are the outbound ranges published in the machine-readable file at https://ip-ranges.atlassian.com. Each entry carries a `direction` field, so filter for…

The dropdown in your template already blocks freeform entry, which is the part you're after for cutting out mistyping. When someone starts the page from the template through the Create menu, CAPA Severity comes up as a Major/Minor dropdown in the fill-in form. They pick one of the two, with no way to freeform it, and their…