Arkadiusz Wroblewski Community Champion

Hello @Tejas Patil As Corrected from @Marc -Devoteam- - My approach isn’t suitable/Contextual don´t fit Into Cloud in this case and don´t wanna provide wrong Solution. I’ll evaluate the solution when I have a free moment.

@최용구 Hello 🤗 This error looks much more like a login/session problem than a “space permission” problem. A key detail is the Hash (17YZ5WN). That’s basically an internal reference Atlassian can use to find the exact failing request in their logs. So keep it and share it if you escalate. Here’s what I’d try in a practical…

Hello @Nikita Grishin What you’re seeing is pretty consistent with how Jira Cloud behaves here: Issue Security is working, but that particular user-search endpoint is not a reliable “who can see this specific issue” check. Why the UI is correct but the API returns “too many” users Jira visibility is basically: Project…

Hello @David Yu If you’re coming from Server/DC, the Cloud model feels backwards at first, but the key is that “users installing apps” isn’t one thing. There are two different risks/controls: Marketplace apps installed by admins (site-level apps) User-connected apps (OAuth apps a user authorizes to access Jira data) Your…

Hi @Albert Chirighin Rather than repeating the usual “pilot + communicate” advice (which is true), here are the real-world gotchas and decisions that mattered most for us and actually drove the effort. 1) The biggest work is “identity hygiene,” not Atlassian clicks Managed Accounts changes who owns identity for anyone on…

Hello @Backoffice team In Jira Cloud, this is usually caused by the dashboard auto-refresh being turned off, a browser caching issue, or the browser throttling background tabs. Here’s what I’d suggest you check: Confirm auto-refresh is still enabled Open the dashboard → … (More actions) → Configure automatic refresh Make…

Hello @r_deepa What you’re seeing is (unfortunately) expected behaviour in Jira Cloud. The Board “Summary” / “Overview” page is a system-generated view and it’s not configurable like a dashboard. You can’t add your own field-based filters (like your custom Customer field) or scope the metrics/lists to “Customer = XYZ”. The…

@Álvaro Boza Great to hear that :)

Hello @Izaskun Ochoa In Jira Service Management Cloud, you can export customer data, but it depends what you mean by “complete database across all projects”: * If you just need a complete list of customers (site-wide), you can export the portal-only customers list to CSV (this gives you everyone registered as a portal…

@Álvaro Boza The error happens because “Time deviation” is a Number field, but the value your rule is trying to write is not being interpreted as a number at runtime (often because one of the source smart values is empty/null, or the calculation is evaluated as text). To fix it, make sure your “Time deviation” edit uses a…

hi @Álvaro Boza Hi @Álvaro Boza Because you only need this in one space/project and you want a numeric value stored on the Epic when it’s closed (so you can use it later for calculations), the best practice is: Use Automation to roll up values from issues that are actually in the Epic (true Epic children). If you also need…

You can contact Atlassian Support here: https://support.atlassian.com/contact/ Then select: Account & Login → Login issues → Can’t access my account

@red888 You’re not missing anything, this is basically how Jira/JSM is designed. In company-managed JSM projects, custom fields are global objects. So if you let non-admins create fields, they’re effectively creating fields that can appear across the whole site, which is why Atlassian restricts field creation to Jira…

Hi @[deleted] Yes, there is still a way to recover access, but it depends on how your Jira Cloud site and account are managed. Since your old email address is deactivated, you can’t receive password reset or verification emails, which means you usually can’t update the email yourself through the standard Atlassian account…

Thanks for connecting. Here goes mines: www.linkedin.com/in/arkadiusz-wroblewski

Hi there @Harrizontal I think I see what’s happening. In Jira Cloud, getting a 404 (“Issue does not exist or you do not have permission to see it”) usually means authentication is working, but the user behind the API token (your service account) doesn’t actually have permission to view that issue. Granting app roles and…

Greetings @Matthias Gaiser _K15t_ and Thank You :)

Hi @Braham Dev That “Something’s gone wrong” banner in Jira Cloud is unfortunately a very generic UI failure message, it usually means the page couldn’t load one of the required resources (auth/session, an app iframe, a blocked script, or a permission-protected API call). A good way to troubleshoot it is to isolate whether…

Hi @Biancha We’re in a very similar spot (Cloud → Cloud, usually selected projects, not full-site). What’s worked for us is treating this as a repeatable runbook with governance + batching, not a one-off “migration event”. Our repeatable approach: * Intake + scope lock * Confirm exact projects in scope (and whether they’re…

Hi @Gerald Preissler For Jira Cloud, there are no fixed IPs you can allowlist. Atlassian Cloud uses published IP ranges that can change, so the supported approach is to allowlist Atlassian’s official ranges (via their JSON feed):…

Hello @Kit Friend Use a “Guest Collaborators” Create a group like guest-collaborators Grant that group Collaborator in the relevant space(s) When inviting guests, add them to that group (can be bulk-managed)

Hello @Matthew Macbeth Thanks for the screenshots, they help a lot. What you’ve done so far (verifying the domain and adding the custom email address in Org settings) is correct, but it doesn’t automatically switch Jira/JSM to send “From” that address. Also, the Incoming/Outgoing Mail screens in Jira admin are mainly for…

.

In Jira Cloud (Jira Service Management approvals), approvals are tied to the workflow status that contains the approval step. In practice, an approval “round” is created when the issue enters that approval status. Scenario 1 The issue leaves the approval status and re-enters it (most common) No field clearing needed. If…

Hi Christina, when a field shows “Locked” in Jira Cloud it usually means it’s a system field or an app-managed field, so Jira won’t let admins change its configuration (and sometimes you can’t edit it the same way as before). A couple quick checks: * Where do you see “Locked”? * If it’s in Admin → Issues → Custom fields…

There isn’t a native, supported way in Jira Cloud to make one specific field (including an Assets / Insight object field) editable only for the project role “Administrators” while leaving the rest of the issue editable. Jira permissions (Edit issue) are issue-level, not field-level, and Assets fields aren’t supported by…

You can’t restrict Create by issue type using Jira permissions alone — the Create issues permission applies to the whole project, not to specific types like “Task”. The clean workaround (no automation/delete) is to block creation via the workflow “Create” transition for the Task issue type: * Make sure Task uses its own…

Super promising. One piece of feedback: it’d be great if the automation UI exposed team properties (lead, manager, channel) as smart values so we can mention/assign dynamically without hardcoding names. Otherwise, the “Team field changed → move to team board + notify” flow is going to be a huge quality-of-life improvement.