Gabriela - LeanZero Community Champion

Hi @Vladislavs Sakadinecs Your first form is the documented one. Atlassian's KB for this exact failure uses the same customfield_XXXXX.ongoingCycle path and says the custom-field-ID version "can be more direct", so that isn't where your problem is:…

Hi @Sumate S_, Confluence does store it, and the editor writes it unasked. I pasted a fenced markdown block into a Cloud page, published, and read the page back over the API: it came back with a breakout mark of mode wide, width 760, which in storage shows up as breakoutMode and breakoutWidth parameters on the code macro.…

Hi @Akshat Redhu, that wording rules out your API key. A call that actually reaches Atlassian and gets refused comes back with the suffix "on http status error", which is what an entitlement or permission problem looks like. Yours says "on request error", the other branch, where the request itself didn't complete. So it…

Hi @Dinesh_Prajapati, your 7 days is right, specifically as the support restore window. Atlassian's backup KB: "we perform hourly snapshot backups of your repositories and store these in AWS. Our support team is able to restore your core repository content within a 7-day window of data loss." On the outage question, no.…

Hi @Quinn Huynh, no admin setting for that, in Jira or in the app, and nothing on either tracker suggests one exists. It couldn't be a Jira-side setting anyway. Look at what Jira actually receives for a PR: the dev-info payload carries the title, status, the two branch names, reviewers and an explicit issueKeys array.…

Hi @Edith Kuhn, first thing I would look at is which URL your mcp.json points at. If it is https://mcp.atlassian.com/v1/mcp/preview, this is expected rather than broken. Atlassian's v2 preview announcement from 1 July puts "Dozens of new tools abstracted behind discover and execute tools" and gives you "Reduced default…

Hi @Chris, both of the things you floated exist. They're different features though, and they don't compose, so it's one or the other. The second one is what I'd build. One database, then a saved view per audience, each carrying its own layout, filters, sorts and Hide fields selection, and you switch by clicking the view's…

Panel is a third case then. CONFCLOUD-83674 is written up for Expand only, and 83258 covers headings inside app macros on the legacy renderer, so a native Panel falls outside both of them. Eight votes on the first one, still Gathering Impact. It won't move on votes alone, so if you can drop your Panel repro onto it, that…

Hi @Michalis Motis, on the admin side there is exactly one OAuth revoke, and it isn't surgical. You uninstall the app from the Connected apps screen, and for a 3LO app like this one "the Uninstall button revokes all users". All of them, at once. No admin control drops a single person's grant. Atlassian's line is that "a…

Hi @Kristina Eddy, when part of a ToC lands and part doesn't, the split usually tracks where the dead headings sit - a heading inside another macro that renders its own body. Expand is the usual one, Marketplace app macros the other. CONFCLOUD-83674 and CONFCLOUD-83258 are both open on those, no fix on either yet. Take one…

It does. I said a missing parent proved little, but yours had one, so run the check. A parent still naming User2's repo means the link is intact and it's all Ben's. Nothing there and it's gone, assuming that was the Fork button and not a clone you pushed up. It still doesn't prove what's emptying the picker. The occasional…

Correction first. JSDCLOUD-16196 is Closed, resolution Fixed, July 2025, so ignore what I said about adding your version to it. The "no known workaround" line there is from the original description. On the alias, no, that isn't expected. Acknowledge is documented to look for an open alert whose alias matches, and only one…

Hi Jean, that 410 is Bitbucket saying it got an app password, so what you refreshed isn't reaching it. A bad or under-scoped token gives 401, so that isn't it. Your gmail hunch is worth pulling on. Sourcetree stores credentials per identity as USERNAME@DOMAIN, and only uses the account ones when the remote URL carries no…

No update from my side, I've no visibility into the ticket Ben raised. Ben, is there an issue key Rachna can track this against? Separate from the banner, something to rule out. You're raising PRs from your repo in your workspace into User2's in his. Atlassian scheduled cross-workspace fork relationships to be…

Hi James, that path does not run inside the plan. Releases live in the space, so you get there from Jira's top nav, pick the space, then Releases in the left sidebar. The Filter dropdown you found is the timeline's own, which is why it looked empty. You do not have to unarchive. You can move those 30 onto an active release…

Hi @Mariam Hovhannisyan, yes, and on that exact version. JRASERVER-79037, mail queue piling up after upgrading to 10.3.8+, filed against 10.3.8, 10.3.9 and 10.3.12. Atlassian puts it down to JRASERVER-78861, the 10.3.8 change that had Jira cache the SMTP connection instead of opening one for every message. Your flush…

One branch worth ruling out before you chase the role: which plan the Jira product itself sits on. You can't edit space permissions or roles on the Free plan for software and business spaces, and a site can carry JSM Standard alongside Jira Free, so Space settings renders exactly as you describe for a reason that has…

There are no acknowledge flags in send2jsm.go because there don't need to be. It's prebuilt, and you don't have to edit it or write custom scripts. And it isn't your setup. JSDCLOUD-16196, "When Zabbix alert is acknowledged, the JSM alert is not acknowledged", reproduces on Zabbix 7.2.0 and above, with no known workaround.…

You can add them. Free caps the site at 10 users and inviting people runs through user management, so that part still works normally. What froze is the role assignment. Depends on the space, though. Team-managed: Space settings, then Access. With the access level on Open, everyone on your Jira site already holds the Member…

I got the full form wrong in my first answer. It doesn't carry the dropdowns. All expanding does is add the rest of the fields underneath, and the space and work type stay up in that header line in both views, so pinning full form wasn't going to give you what you asked for. What brings the labelled Space and Work type…

Hi James, that panel only counts removals, so anything hidden at the view layer never appears there. And the days-since-done rule only applies to work items from company-managed spaces, so if any of the 30 sit in team-managed ones, 365 was never going to move them either. Quickest way to settle it: Plan settings, Work in…

Hi @james_vanderhaeghe, the root smart value is forms, plural. Your Create variable step has {{form.last.loyalty-origin}}, so nothing lands in {{teamname}} and the edit step has nothing to write. The dropdown needs one more piece on the end. Choice fields hand you the option, and the text you see comes off its label. Try…

Hi @Dion Duimel, not a bug and not your account. Free Jira can't assign space roles, and approving a join request is a role grant, which is why add roles sits greyed out behind an upgrade prompt for you and for the other admins too. Coming down from paid is what makes it bite. Atlassian's page says schemes and space roles…

Hi @Laura_Whaley, that's the new Create modal. Quick Create became the default when it started rolling out to Jira Cloud sites mid-July, and the old full form with the dropdowns is still there behind the expand icon. To make the full form your default, open it, then More actions (•••) inside it and toggle on Always open in…

Hi @santhoshkumar_sethi, nothing to acquire from Atlassian, your own org admin makes one. Atlassian Administration, Directory, Service accounts, Create a service account, then give it the Confluence role. No seat cost, they don't count towards your user limit. Then pick the account, Create credentials, API token, set an…

Hi @Nivitha Titus, create and close working while updates don't points at an empty Update Operations table. In a Zabbix trigger action the three tables fire on different events. Operations on the problem, Recovery Operations on the resolve, and the third one on an acknowledgement or a severity change. Yours is wired for…

Hi @Dominique QUINTON, Atlassian hasn't named a replacement for it. The Time Tracking report is one of three still on the retirement list, with User Workload and Version Workload, and Ben Payne at Atlassian gave the reason: "we've received minimal feedback around the usefulness of these reports so will still schedule them…

Hi @Christoffer Rosenkrands, automation can't do that part. Confluence automation has no attachment action at all, and the copy page docs spell out that attachments don't come along with a copied page either. Nothing can fire on a file turning six months old. The move is native but manual. On the page use Show details in…

Hi @Mangesh Bajirao Pangavhane, the extra rule you were trying to avoid is the only shape that works here. Nothing on your side is misconfigured. Atlassian's Rovo agent tools page states it directly: "If an agent is triggered in an automation flow, it cannot use its own tools; it can only provide a text response which can…

When you run it in the test project, the reset lands as a new cycle rather than a continuation of the old timer, which is where the fresh 24 hours comes from. The old ones aren't lost. Expand the SLA name in the SLAs panel and each past cycle sits there with its elapsed time and whether it breached, so the juggle leaves…