Gabriela - LeanZero Community Champion

Yeah, you're not alone. This is the expected outcome of the Field Schemes migration, not something you broke, and plenty of context-heavy sites are seeing the same jump. The migration keeps the exact same fields available in every space and work type you had before. A lot of your per-project field visibility was really…

Hi @Corinne Guibert, this is what service accounts are built for. Move these integrations off personal accounts onto a service account in admin.atlassian.com under Directory > Service accounts. There's no person attached, so nobody's vacation or departure can break a script, and it doesn't consume a Jira or Confluence…

Olha's route is a fair one. A forms app that runs regex or an extension check on the attachment field is one of the few ways to enforce a file-type rule, so that's a sound direction. The piece missing from the thread is the native side. Out of the box, JSM Cloud forms give you no way to limit an attachment field to certain…

Hi @Max Mycroft. The validator only checks the file's structure, so it can't tell you whether the build or the FTP step will actually run. That's the gap you're hitting. Atlassian doesn't offer a way to execute a whole bitbucket-pipelines.yml locally as-is. What works is reproducing a single step by hand. Pull the same…

Thanks Karen. Good detail. If it's missing from the Task Report for that page too and you've got edit rights, then permissions and the @mention aren't the blocker here, which points at the task not being indexed. First thing I'd try is to open the source page in edit and publish it again without changing anything, since a…

Hi Daniel — both show because JSM has no in-place email change for a customer, so updating the record didn't rename the old account. You now have two separate customer accounts, one per domain, and the reporter picker lists every customer on the site, so both keep surfacing. Marc's right that if the account is unmanaged…

Hi @Jan Milata, your read is correct. Atlassian Guard only supports SAML 2.0 for account-level SSO, and OIDC isn't available for that in Cloud today. Native OIDC is tracked as a feature request, ACCESS-625, currently at "Gathering Interest". Atlassian hasn't committed a delivery date and I wouldn't read a timeframe into…

Hi @Basil Ali Khan, welcome to the Community. Nothing in your nginx logs means Jira Cloud isn't reaching your public endpoint at all, so the break is between Jira and your server, before nginx sees anything. Two common causes. The n8n Jira Trigger registers the webhook in Jira using whatever base URL your container…

Hi @Mini Channanathil, Peter's approach is the right shape here — the page-created automation with a review label, plus a native review marker. A couple of specifics to add. Page-created events do get logged, but in the org-level audit log at admin.atlassian.com, under Audit log. The per-space Confluence audit log only…

Hi @Calvin, your read is right, JSM does try to catch these. The email processor drops anything whose headers carry Auto-Submitted set to anything other than 'no' (auto-generated, auto-replied, auto-notified) or Precedence: bulk, which filters most OOO replies before they ever become a comment. Outlook ones slip through…

Gor's already put his finger on why the Edit action wasn't updating, and that part's correct — in the ternary it needs to be {{issue.Story Points}} without the quotes, and the comparison values catch people out because the field can come through as 1.0 rather than 1. Easiest way to pin it down is to drop a Log action…

The other two replies have the fundamentals right, so I'll build on them for the part that hits your app. That field type, com.atlassian.servicedesk:vp-origin, is a locked custom field. Locked fields are created and owned by the app that installs them, and an admin can't create, configure or delete one through the UI or…

Hi @Kristy, welcome to the community. "Create with shared configuration" sets project A up on the very same schemes project B already uses: the workflow scheme, issue type scheme, screen scheme, field configuration scheme, plus the permission and notification schemes. Each one is a single shared object, so editing it…

On the editing side, Confluence Cloud won't co-author an attached Office file in place, the file is stored outside Confluence, so whoever saves last ends up on top. If you want genuine simultaneous editing, the practical route is to keep the file in OneDrive/SharePoint or Google Drive and embed or link it on the page, so…

I'm with Walter on this one, a working agreement tends to stick better than a hard rule, because the moment a convention feels like bureaucracy people quietly start gaming it. That said, a shared shape does pay off, and Rustem's 'Product | Component | Action' pattern is a good example of one, it gives you context straight…

Hi @Fabricio Riveros, welcome. Jira has no native per-issue carryover counter. The Sprint Report (Reports → Sprint Report) has an "Issues Not Completed" table per sprint, so you can see what rolled over in a given sprint, but nothing aggregates that across sprints for one issue. A running count is workable because the…

Hi @Stephanie Blair Yes, this is built in, no app needed. On a company-managed workflow, open the workflow, click the transition between the two statuses, and under Validators add a Field Required Validator pointing at your checkbox field. It blocks the transition whenever that field is empty, and for a multi-select…

Hi Daniel. Connection fields don't hold a value in the custom field, the link between ideas is stored as a normal Jira issue link, so Edit issue (advanced JSON) on customfield_15205 has nothing to write and runs clean without changing anything. Swap that action for Link issues and link the current idea to the target one,…

@jeremy wood Karsten's pointing the right way, keep this in the workflow. Be careful with marking Team required in the field configuration though. A required field that isn't on the request form makes portal submissions fail, and the error only shows up in the browser console. Add a Field Required validator on the…

On the status one, that's expected behaviour and it explains what you're seeing. The four statuses you set under Space Settings > General > Avatars and status only control the page content status, the label that sits above the page title. That's the one that shows just your four options once you've turned off custom…

Hi @Ryan Farnell, submodules don't inherit the parent clone's credential, so Jenkins fetches them with whatever's saved separately, usually still an app password. That's why it only broke today: the brownout returns 410 for app passwords during its windows, so the main clone rides through on your token while the submodule…

That template comes from Atlassian Analytics, which runs off the Atlassian Data Lake. It's a separate thing from the normal gadget dashboards, and that's usually where the confusion starts. Analytics and the Data Lake it needs are Cloud Enterprise only (Jira, JSM or Confluence Enterprise), with a Data Lake connection that…

The person who approves this is your Atlassian org admin - you can't switch it on yourself. A couple of things feed into it: 1. Whether Rovo/Studio is turned on for you at all. An org admin controls that at admin.atlassian.com > Rovo > Rovo access, where they can block it by app or by user group. If your group's blocked…

That "works off the brownout, dies during it" pattern is the giveaway — the credential you've got is still an app password. The brownout only knocks out app passwords (git over HTTPS returns 410 during the windows), so anything that lines up with the brownout exactly is app-password auth. A proper API token rides straight…

Yeah, there is. For Bitbucket Cloud the main route now is the Give feedback option in the product help menu — that's where Atlassian collects suggestions since they stopped letting people file tickets directly. The public tracker still exists too, the BCLOUD project on jira.atlassian.com. You can't create a new suggestion…

Native automation can't see Workforce's availability, so you have to build the shift logic into the rule yourself. To do it without an app, branch the escalation rule on the current time and send each branch to only the agents on that shift. In the rule that clears the assignee and sets Team to L2, add If/else blocks keyed…

@Dave Matthews if you want the list to stay live and selectable on the published page, the template variable won't get you there, but a Confluence database will. Create a database in the space, add a Tag or Single select field with your options, then embed it on the page — each entry keeps a clickable pick-list you can…

@Dan's got the right ticket — CONFCLOUD-84547 matches this exactly: the live page gets emptied when the collaborative editor snapshot isn't available, with no version entry and no disconnect warning. That's your symptom. Small correction on the fix status though. Last I looked the ticket was still at Waiting for Release,…

Hi @Chris Kourpas Ajay's right that there's no native "auto-approve on comment resolution", and honestly I wouldn't expect one — the approval is meant to be the reviewer signing off on the whole change. For the typo case you can still get most of the way there without waiting on Dave. Have the reviewer approve in the same…

Hi @Peter Lie, welcome to the community. That copy-from-List-view trick got reworked recently, so the dependable route now is the issue search export, not the Timeline or a board (those two drop subtasks and won't carry a layout). Go to Filters / your Issues search and run a query that returns subtasks too — querying the…