Arkadiusz Wroblewski Community Champion

Hello @Mateusz Glanowski Sorry to hear that 😢 I feel your pain but this is one of those cases where the community can only point you in the right direction. We can’t reactivate Confluence, fix the “Unable to add app” state, or recover data from the backend from here. For deactivation + recovery, you really need Atlassian…

@Alan Bruce Yep it’s not just you. If you’re sitting in Admin/Automation/Assets all day, you’re basically the first one to feel every little Cloud wobble. What’s going on is pretty simple (and a bit frustrating): Cloud is always moving. Atlassian ships changes continuously and rolls them out in waves. Most weeks it’s fine,…

Hello @rworkman Yep I know exactly what you mean. What you built works, but it’s basically an Asana checklist recreated with subtasks, and Jira gets messy the second someone writes a long request title. If you want best practice (and something your creatives won’t hate), I’d do this: 1) use the workflow for the process…

Hello @arti_b_patil In Jira Cloud, a Component is basically a project-level bucket you assign to issues to show which part of the product/service the ticket belongs to (module/area/team), like UI, API, Billing, etc. Important part (and why it’s different from “just a field name”): Components is a standard Jira…

Hello @chickpeafilae In my experience: start with Jira Automation and only go to ScriptRunner when you hit a wall. Use Jira Automation when: it’s the “usual” stuff: copy/set fields, auto-assign, create sub-tasks/linked issues, simple conditions, scheduled cleanup, notifications, routing, basic workflow helpers you want…

Hello and welcome @Michael Canaday Yep, that can happen and it doesn’t necessarily mean someone “manually invited” her today. In JSM Cloud, that invite-style email can get triggered again when Jira thinks the customer needs to (re)confirm portal access. The usual reasons I’ve seen are: Account/identity changes in Atlassian…

@funnystyle That’s one of those cases where there’s no “community fix” unfortunately, only Atlassian Support can confirm what happened and restore anything (if a restore is possible). So I wouldn’t spend too much time troubleshooting. I’d go straight to admin.atlassian.com → Support and open a ticket. Include: your site…

@Kris Klima _K15t_ Haha, and now you're working for one of them. You’ve come full circle 🤣 But that’s how it goes in this community and the Atlassian ecosystem. Often, a company you were once a customer of becomes your employer in the future. And then comes the interview question: “Did you know our tool?” Oh yeah I’ve used…

@Tinker Fadoua @Kris Klima _K15t_ @K15t GmbH and @Appfire Support Haha, you can see from the Open Ticket link that this has cost me quite a lot, an tons emails with very detailed bug documentation and extensive cross-team cooperation between Appfire K15t and Atlassian. But I’m happy we’re nearing the end, and I’m impressed…

Hello @michael_blake Yep, that can happen even if nobody on your side touched anything. Atlassian has been moving Confluence Cloud away from the legacy editor for a while, and part of that rollout is that they auto-convert remaining legacy pages to the Cloud editor. So it can look like the timeline suddenly changed, but…

Hello @Casper Leung Yep, I’ve seen this exact thing after the legacy - cloud editor auto-migration: the page looks fine while you’re editing, but once you hit publish/save the view/rendered version breaks. It’s usually some legacy layout/macro markup that doesn’t convert 100% cleanly and only shows its “real face” on…

Hello @damir_khamidullin Yep, your assumption is mostly right not because Atlassian “deprecated” tabs, but because the New Issue View doesn’t handle screen tabs the same way the Classic view did. In Classic, tabs were a reliable way to group fields and keep that structure visible on Create/View/Edit. In the New Issue View,…

Hello and welcome 🤗 @michele_wilson On Android you can move issues between columns, but you generally can’t reorder the columns themselves from the app UI that configuration is done in the web experience. Atlassian’s Android board docs focus on rearranging/moving issues, not changing column configuration. Mobile Browser…

@Marc -Devoteam- @Tejas Patil As promised. The most reliable way I can think of is doing it with a trigger + an IF condition, then create the sub-task, and after that use a Branch rule (Related issues → Most recently created issue). Inside the branch you just add a few small IF blocks to copy only the matching components…

Hello @vasanth Here you go, it’s a pretty detailed list, but the key point is: Enterprise removes the usage cap (executions), not the operational/service limits. The operational limits still apply to protect performance, and rules can be throttled if they’re exceeded.…

Did you Checked Request Participant Permissions ?

Hello @Emiliano Reynoso As @Mikael Sandberg told you, this info popup appears when you try to edit groups that are provisioned from your IdP (e.g., AD / Entra ID via Atlassian Access / SCIM). If you think about it a bit deeper, it’s actually consistent and makes perfect sense: Why should Jira allow you to change a group…

Hello @Shanmuga Narayanan Pitchaipillai and @Bisharat Ullah Khan As I understand you both, I can relate to why Atlassian made this change even if I’m not personally happy about it. We have to live with it, because Atlassian provides great tools. In the end, the naming is mostly cosmetic. The main reason was the…

Hello @Brian Nørvig If the agent can’t search users in a picker, Jira Cloud typically requires the global permission “Browse users and groups.” Without it, user pickers often still show already assigned users but won’t return search results when trying to add new ones. Atlassian documents this behavior and the fix here:…

@Aggeliki K Unfortunately, Jira Cloud doesn’t support this at the moment due to custom field limitations. I ran into the same situation in Data Center, where we used cascading fields (via ScriptRunner). Yes, Sebastian’s approach is correct. The quickest solution would be to use ScriptRunner. Jira Service Managment are…

Kansas - Carry On Wayward Son. Supernatural Fans Recognizing it Directly. Still Legendary.

Hello @Jack Yu Any Chance it land into Standard Subscriptions ?

Hi @Marc -Devoteam- I didn’t use AI for that. You’re right for native Cloud Automation: Edit issue can’t target another issue by key it only edits the issue in scope. The reason it “feels possible” is that in Data Center (or with apps like ScriptRunner) ( and im steel Deep into Hybrid between Data Center and Cloud with…

Hello @PANKAJ MISHRA What you’re seeing is expected in Jira Cloud Automation. When you go into a branch (“for each issue…”), Automation is basically running in a separate context. So even if you “append” to a rule variable inside the branch and you can see it growing there, that change doesn’t reliably carry back out to…

Hello @Ashwin Kurundkar Dashboards don’t really “belong” to a project the way boards do. In Jira, a dashboard is basically a shared page so you control access by changing its sharing settings. What to do: Open the Scrum dashboard Click … → Share dashboard (or Edit dashboard) Remove anything broad like Public / All…

@Nikita Grishin Totally fair point. After doing all the work to configure Issue Security, you expect an API called “users who can view this issue” to return only the people who can actually see it. I’m not going to be too critical of Jira’s permission model though. It’s one of the few platforms that gives you this level of…

@Nikita Grishin Please let us know about answer you get from support, API Endpoints are very living environment, especially since latest 2 Years changes which have very Big impact on many things.

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…