Gabriela - LeanZero Atlassian Partner

Hi Kassegnin, Yes, the option you picked gives your customers this for new requests, if your space's own switch is on too. I tried it on a test site, portal only. It's Space settings > Access > Customer permissions > Customer sharing > "Allow customers to share requests with organizations they are a member of", and with it…

Hi Harry, that status move isn't part of the comment; it normally comes from an automation rule JSM creates with the space, "When a comment is added → update the status", so I'd open it under Space settings > Automation and read its audit log for one request that stayed put (on a space older than Aug 2021 it may be…

Hi Joanna, I rebuilt your rule on a test site and got your audit log line, "No related issues could be found", from a single-space rule, whichever branch I used: linked work items, most recently created or JQL. Swapping the branch type can't fix it. With the second space in scope, as Trudy described, the same branch worked…

Hi Normann, JSESSIONID won't separate them. Tomcat hands that cookie to anonymous visitors too, which I'd guess is what your cookie matching ran into. The one that only exists after a login is seraph.confluence, the Remember me cookie. Atlassian's cookie page says Remember me is "enforced by default when Confluence is…

Hi Manuel, In a team-managed space an epic doesn't show as a card on the board, whatever status it's in. Atlassian's KB says so: "Performing these steps in a Team Managed project does not make the Epic visible on the board. Here you need to use the Timeline or Epic panel to view the Epics." On the board I'd use Group >…

Hi Kevin, Going by Atlassian's own tracker there is an opt-out for in-product promotions, though it's something their support team applies for you and not a setting you can reach. On JRACLOUD-97215 an Atlassian product manager wrote on 19 January 2026: "We currently have an internal tool that facilitates site-level opt…

Hey @s-umekawa, sorry: I tested with no login, on public repositories, so my API token tip for a private wiki was untested. Your 403 means the token was accepted and then failed a scope check, which doesn't tell you whether the wiki is still there. I'd try SSH next, because SSH keys have no scopes. Add a key under your…

Hey @harvizzle, thank you for writing this up, and sorry it took me a few days to get back to you. A scheduled run has to be seen creating something on a real site, and ten days is a painful way to learn it. I tried the same endpoint on a test site at the weekend. With no login at all and no accountId in the body it comes…

Hi @s-umekawa, I'm afraid there isn't much left inside Bitbucket itself. Atlassian removed both features on 20 August, and the update on the sunset announcement says users "will no longer be able to interact with either of the features via the UI or API", so the issue export went with them. I couldn't find temporary access…

Hey William, the weak old Dell made me smile :) I'm curious what you've got running on it, is it a small quantised Qwen?

Hey @Glenell Rosburg, sorry I went quiet on you here. Your screenshot has "Only user actions can trigger this flow" selected, so that rules out my idea about the rule setting itself off a second time, and I was wrong on that one. If you're still getting the two Health stories, the Automations panel on each of them that…

Hey Evie, I'm only catching up on the forums now, so this was a lovely thing to come back to. Thank you, and congrats to everybody on the lists, especially those of you who kept answering right through the platform move.

@Leanne Asanuma, a fair correction from Sami, and I should have been clearer. Atlassian's usage page dates the extra usage billing to December 3, 2026, but it doesn't say whether the pause at 100% of the new organization-wide allowance applies before then, so I'd start where Sami points: Jira Settings > System > Global…

Hey @Parag, you can reach them at https://support.atlassian.com/contact/ and pick the account or admin category, and as a site admin you should be able to raise the request directly. Before that, it may be quicker to try the verification yourself, because it's mostly a DNS step: in admin.atlassian.com go to Directory >…

Hi Leanne, Trudy's steps will find the requests you missed, so I'll only add the part about getting automation running again, because the limits changed recently and the fix may sit with someone other than a Jira admin. Atlassian now meters automation as steps pooled across your whole organization, and its usage doc is…

Hey @Parag, thanks, that narrows it down. With an unverified domain and an unmanaged account, no site or org admin can delete or rename that account, because it belongs to the person and not to your organization. The owner of the old account can delete it themselves from their profile at id.atlassian.com, and after the…

Hi Parag, what you're seeing is expected, even if I know it's annoying. An email address belongs to one Atlassian account, and removing someone from your site only takes away their access while the account itself keeps existing, so when you invite that address again Jira brings back the same account, with its old name and…

Hi Aakash, yes. Sharing a database backup is an official FastShift option, and Atlassian's roles and responsibilities page recommends it "for the fastest migration time", where you provide the backups and attachments and they handle the technical details. The same pages describe what happens to it: the backup is restored…

Hi, I'd add that the limits themselves changed recently, which shifts where Gor's savings actually land. Atlassian has moved automation from per-app monthly run limits to steps pooled at the organization level, and its usage doc says that "every trigger, condition, action, branch, and loop that runs in a flow counts as a…

Hey @yaron, that fits the log-only reading, since the steps after it still run even while the execution sits at In progress. Support is the right place for it now, and if they tie it to AUTO-2095 or give you a new ticket, I'd love to hear which, because it would help anyone who finds this thread later.

Hey @Andre, glad JMX sorted it, and thanks for coming back to confirm, it helps the next person who hits the same error after an 11.3 upgrade. If you have a minute, a vote on JRASERVER-79028 is worth it too, since it's still open without a fix version.

Hi Raxa, Carlos has the why, separate updates start separate runs, so I'll add what I saw when I tested the usual fix on a test site today. The guard most people reach for is a condition that a label such as processed is absent, with that label added as the very first action. It held when the updates were five or more…

Hi Jiahao, there's one condition in Atlassian's own KB on phased migrations that I'd add before you rely on the automatic restore, because it's easy to miss when the waves are months apart. The links are only recreated when both projects go from the same source to the same destination, so if any wave passes through a…

Hi Larry, I rebuilt your rule on a test site with your sample text, and the piece that breaks it is the .first at the end. The regex itself is fine. With a single match, match() already hands back the captured group as plain text, and calling .first on that returned nothing in my test, so the variable was empty and the…

Hey @Glenell Rosburg, one block with else-if is what I meant, so that part's fine, and thanks for ruling out a second rule. Your scope answer gives me another idea. The setting Trudy asked about sits in the rule's details panel (Atlassian now calls it Flow details, the same panel where you rename the rule), as a checkbox…

Hi Davide, I couldn't find that "Retry read net message" stall documented anywhere, including Atlassian's public bug tracker, so I can't point you at a known fix, but the setup doc does suggest where I'd start. The Agent IP Range is described as the range "that will be checked for available Discovery-Agents", so the tool…

Hi Gianluca, since the entries are still there and the All tab shows the old and new values, the change is stored correctly and it's the History tab's display that's dropping them, so I'd treat it as a bug and not something in your configuration. The data itself is safe. I looked through Atlassian's public tracker this…

Hi Brian, the exact 3-to-1 ratio makes me suspect a unit difference and not a wrong value. As far as I know, Jira doesn't keep "3d" as days; it converts the estimate into an amount of time using the Working hours per day setting under Time tracking, which is usually 8, so your 3d is stored as 24 hours. If the gadget then…

Hey @yaron, that sounds like a good plan, and I'd be curious how the JQL condition version behaves on your two sites. If it also sits at In Progress while the field quietly updates, I'd add that detail to AUTO-2095 together with both site names, because it would show the group check itself isn't what holds the execution…

Hi Glenell, before you simplify any further, I tested an If/else block yesterday with two else-if branches whose conditions both matched the same work item, and only the first matching branch ran, so I doubt tighter conditions inside one block will stop the second story. Two separate blocks did both run in my test, so if…