Gabriela - LeanZero Community Champion

Glad you got it sorted, @Jorge Ortiz García, and thanks for coming back with what actually fixed it. That's a useful signal in itself: when a fresh token doesn't move it and a clean reinstall does, it was local SourceTree state, not the auth method. For anyone landing here later with the same "logged in but every pull…

Hi @Karen Macias, welcome to the Atlassian Community. On Data Center the usual cause is the assignee rule: a task belongs to the first person @mentioned in it, so if your name isn't the first mention on that task line, it won't land under Profile > Tasks > assigned to me, and a later mention won't reach you. The other…

@Marc -Devoteam- agreed, and I think these stack rather than conflict. You're right that the initial OAuth consent needs a Global or Privileged Admin to approve the Atlassian app - a standard user can't self-consent in a locked-down tenant, so that grant is step one. My point was the layer after it: even once consented,…

Hi @Aditi_Awasthi, Brita's steps are spot on — you're just blocked on the permission, and that's not something you can switch on for yourself. "Delete Own Attachments" is set in the project's permission scheme, which only a Jira admin can edit. So you'll need to ask your Jira/site admin to add your project role to the…

Hi @Linae Luong Trudy's right that Standard's basic Timeline can't add columns or print a date value beside each item. That column/field display only exists in Plans (Premium/Enterprise), which is what those other posts were describing. What Standard does give you: each schedule bar spans Start date to Due date, so the due…

Hi @Jamie Stanczyk, the reason adding someone to Team B exposes the whole backlog is that Browse Projects is all-or-nothing — right now it's your only visibility lever. In a company-managed project you can go per-issue with an Issue Security Scheme: build one level containing Project Role (Team B) plus Current Assignee and…

Hi @Dave Matthews, welcome to the community. This is expected rather than a browser issue. A List variable never renders as a live clickable list on the finished page; it's only a fill-in prompt. It shows up when you start the page from the template through the Create menu and pick your template, which opens a form where…

Hi @stewart_Emily_Global D_T, Two things are sinking your attempts. filter(v -> …) is Jira-expressions syntax, not automation smart values, so that line just renders empty; automation has no lambda filter. And .name.match(…) collapses the list to plain text, so there's no version object left to read .releaseDate from. Keep…

You're right, my earlier answer was off - I pointed you at the native Create from Template macro, but the one you're describing isn't native. Confluence has no built-in "Create Page" macro and no Parent parameter. That macro comes from ScriptRunner for Confluence (Adaptavist) - its Create Page macro is the only widely-used…

You're right — if your Default scheme already has Sub-task, my first suggestion doesn't apply. This is a real Data Center bug, not just your version: the Move Sub-Task wizard validates the target type against whatever the database has flagged as the default issue-type scheme, not your project's scheme (tracked as…

Hi @Area Sistemi. Yes — a standard Exchange Online user mailbox works and is actually what Atlassian recommends over a shared mailbox, because OAuth authenticates directly as that mailbox rather than impersonating it. Enable IMAP on the mailbox in Exchange Online, then connect using its own credentials; that mailbox…

The token type is almost certainly it, @Jorge Ortiz Garcia. A plain API token is rejected for Git — it has to be an API token with scopes. Create it at Atlassian account settings > Security > Create and manage API tokens > Create API token with scopes, pick Bitbucket as the app, and tick read:repository and…

Hi @Andy Fieweger, glad the field ID checks out, so it's the write that's failing rather than the trigger. Setting a JPD date field from automation with a JSON / {{now}} value is a known one that errors, and Atlassian has a KB with the exact value format to put in the Edit issue action:…

Hi @Anna Patrizia Molero, welcome to the Community. Jason's on the right track. Installing Timesheets for Jira registered it as your site's time tracking provider, so Jira replaced the native log-work field with the app's own widget, and that's what's rendering blank on the issue. To unblock the whole team now, revert it:…

Hi @Konrad, welcome to the community. For E2E tests that just hit the REST API as a user, drop 3LO in CI and the rotating-token problem disappears. Use Basic auth with an Atlassian API token — `Authorization: Basic base64("email:api_token")` — it doesn't rotate, so it sits fine in a secured Bitbucket repository variable.…

Hi @Jorge Ortiz García, welcome to the community. This is the app password deprecation, not a real login problem. Bitbucket Cloud is running scheduled brownouts through 27 July and removes app passwords entirely on 28 July, so SourceTree still shows you connected while the pull fails. Changing your password or re-saving…

Hi @David Shahbazyan, it's not the required fields, those only show up on the later update-fields step. On Data Center the Move Sub-Task wizard validates your target type against the Default Issue Type Scheme, not the project scheme you already checked, and Jira Software's default scheme doesn't include Sub-task. That's…

Hi @Daniel Deak, you're not missing a toggle, this is intentional. Atlassian replaced the old split-screen detail view with Preview Panels across Global Search and List views, and there's no native setting to switch back. The only route to the old layout right now is the temporary site opt-out Atlassian links in their…

Hi @Thomas de Bruijn, this looks like a duplicate of your other post, so I answered it in full there: Create Page Maco "parent" not working. The gist: the Create from Template macro has no parent parameter, so the new page lands under whatever page the macro sits on; pages dropping to the space root is the known…

Hi @Thomas de Bruijn, that's the macro working as designed, not a broken setting. The Create from Template macro has no parent or directory parameter. The new page becomes a child of the page that contains the macro, and Space Key only chooses the space. So if pages land at the root, either the macro isn't sitting on the…

Hi @DIDA KHARISMA AKBAR Germán and Marc are right that your list is missing entries (recaptcha, gravatar, LaunchDarkly, Sentry, Statsig, teamwork-graph). Rather than hand-maintaining it, which will always drift, pull from Atlassian's own maintained reference. It's split into an Atlassian domains section and a Partner…

Hi @Utsav Kothari, Germán's two filters are right for the MTD/YTD scope, but the assignee-by-status breakdown you're after doesn't come from the JQL. Point the Two Dimensional Filter Statistics gadget at that saved filter, then set Y Axis to Assignee and X Axis to Status. The axes do the grouping; the filter only scopes…

Hi @Andy Fieweger — Gor's route works, but the cleanest way to verify the exact ID Rovo handed you is to open https://your-site.atlassian.net/rest/api/3/field in a browser while logged in, then Ctrl+F for your field name. The value beside it, customfield_XXXXX, is what your automation should reference. That endpoint lists…

Hi @Kobus, welcome to the community. For moving a whole project with all 100+ tickets between two Cloud sites, skip CSV as your main route — the native transfer keeps comments, attachments and history that CSV drops. You'll need org-admin (or app-admin) rights, then go to admin.atlassian.com > Data management > Data…

Hi @Cristian Zuccalá, welcome to the community. Changing the timezone didn't actually alter your sprint. Jira stores the start and end as a UTC instant, so switching from GMT+2 to GMT-3 only re-rendered that same moment in the new timezone; the sprint data is untouched, just the shown times moved by the 5-hour offset. If…

Hi @Harish B_N, welcome to the Community. Manoj and Tomislav are right that this is a permissions question — the exact setting to point your admin at is the one governing agent creation in Rovo Studio. By default anyone with Studio access can create agents, but an admin can lock it down: in the Studio app, Settings >…

Hi @David Yu — the release notes you had in DC do still exist for Cloud, just in a different place. Arkadiusz and Ren are right that Cloud apps auto-deploy as SaaS, but the version history you're after sits on the app's own Marketplace listing: open the listing, hit the Version history tab, and each release shows a date…

Hi @Michael Smith, Gor's right that the connector uses a fixed OAuth scope set, which is exactly why editing the scopes on the authorize screen throws "Error authorizing OAuth." There's no Atlassian-side toggle to index articles but skip tickets. The lever sits on the Zendesk end. Teamwork Graph only ingests what the…

Hi Susannah, that's working as designed rather than a bug. JSM's Opsgenie engine dedupes purely on the alias of any open alert, account-wide, so the source integration or API key never factors into the match. To keep your machines separate, open the Grafana integration's Advanced settings and edit the Alias field to append…

Hi Casey, you can keep those accounts connected and just pull their results out of search, no need to disconnect anything. As an org admin, go to admin.atlassian.com, then your org > Apps > Connectors, expand the site, find the app (Slack, Google Drive), open the ••• More actions menu > Manage, and switch off "Show results…