Arkadiusz Wroblewski Community Champion

Hello @Jakub Sławiński Please look into this KB: https://support.atlassian.com/subscriptions-and-billing/docs/understand-billing-administration/ https://support.atlassian.com/subscriptions-and-billing/docs/understand-the-improved-atlassian-billing-experience/ 

Hello @Lubomir Glinsky We can point you to a few things, but first we need to know what you’re struggling with. 🙂

Hello @Konrad P. Campbell From what Atlassian currently documents and my Experience with Teams Integration, there is no native Jira Automation action to schedule a Microsoft Teams meeting. What is supported natively is: * sending a Microsoft Teams message from Automation * using the Jira app in Teams for notifications and…

Hello and Welcome @Henry Hughes There was recent changes to the Linked work items section in Jira Cloud which are Deployed from last couple Weeks.

That´s why theres always multiple Possibilities :)

No thanks. As my Mentor said, "Make Love, not Warcraft" :D

Hello, indeed, I checked it twice now and also found a feature request. https://jira.atlassian.com/browse/JSDCLOUD-1269 Indeed, it’s one of those fields that cannot be bulk changed. So you have two options: use Automation with a tight JQL scope for the tickets you need, or use the REST API.

@Kris Klima _K15t_ Golden Rule - Try Solve problem first before you grab workaround 🤭

@Jeffrey Bistrong I would be careful with external apps as the solution here. Atlassian says that once a custom field is tagged for deletion, it is also removed from automations, workflow functions, and third-party apps that use it. So this is really more a preserve-the-data-before-deleting-the-field task than an app…

Hello @Maria Scotti @Ollie Guan You have right but I see here other problem... Since the Delete option is missing in page history, this looks more like a permissions/admin access issue. Atlassian documents that page versions can be deleted from Version history, but only if the required access is available. Because the page…

Hello @Mar For field updates, Atlassian points to Search / Bulk change, and notes that the available bulk edit operations depend on the selected work items and the fields involved. Edit - Not really, that´s one of this Fields which cannot be "Bulked"

Hello and welcome @Babar Brohi It would be helpful if you narrow more for what you looking for? My rule of thumb is to start with the simplest possible automation and only add complexity when there is a clear benefit. In Jira, a lot of repetitive work can already be handled with native automation, for example: field change…

Hello @Paul Liebrand There is not one single Atlassian best practice for this design, so this is more my recommendation based on maintainability than a hard product rule. My usual approach would be: * keep one standard onboarding/offboarding request type for the common process * use conditional fields / form sections for…

@Latoya Dillon You're welcome and I wishing you good Luck and much Fun. Automations besides of Work are always real fun especially when they working as intended 🤗

@Latoya Dillon Yes, I would create them as separate rules, not as one nested rule. For your use case, the logic is quite clean already: pages with ABC in the title → apply restriction set A pages with ZYX in the title → apply restriction set B So there is not much benefit in combining that into one larger nested rule.…

@Latoya Dillon That's making everything clearer. Then the way to do it is with automation + page restrictions. Create a rule for pages where {{page.title}} matches ABC, then use Restrict page to give edit access to the correct user/group. Do the same for ZYX, etc. Confluence supports restrictions at the page/content level,…

@Jordan Capola There is no separate toggle in the agent view for this. The relevant setting here is Strip quotes under Email requests. That controls whether Jira Service Management keeps the full quoted email thread or only the latest reply when customers answer by email. So if the issue is that every customer reply brings…

Hello and welcome @Latoya Dillon This is a Confluence limitation, not an automation one. In Confluence Cloud, edit restrictions are applied at the content/page level. Atlassian’s documentation describes restrictions as content-level or page-level controls, not section-level controls within one page. So if different users…

@Félix BOULE--REIFF My answer is still stay same, your answer about Standard and usage in free Tier doesn't make much sense. There's two options. You paying and are on standard or use free version. About screenshot, I don't think so. Even big companies with proper configuration will have problem to hit this limits, so if…

Hello @Félix BOULE--REIFF On the Free plan, I would not start with request types or portal settings. If portal, customer access, channels, and self-service all stopped working together, this sounds like Jira Service Management itself is no longer fully active/available for that project. My first checks would be: * whether…

In most Cases even only to Admin, since Tickets are not "Thrashed", that Permission must be scoped very Carefully to avoid Data Loss, or "Angry Fired Employe Story"

Hello and Welcome @hschoenen First: That you are Admin doesn´t always Automatically mean you have all Permissions. Second: Please take a look here, quite similiar Topic with most Answers you need. https://community.atlassian.com/forums/Jira-questions/Unable-to-Delete-or-Archive-Jira-Tasks/qaq-p/3205515#M1172180 

Unending Football playing with Schoolmates..... Still remember that well....

Hello @Utti Stevens In most cases, you cannot simply access that Atlassian account without the login details just because it was created with a former colleague’s email address. The main question is whether this is a managed account in your Atlassian organization. If your company has verified and claimed the email domain,…

Hello @Sascha This is not something you can do directly with the native Assign to Current User Workflow post function, because it does not support an extra condition like “only when Assignee is empty”. The usual workaround in Jira Cloud is to move this logic into Automation: * Trigger: Issue transitioned * Condition:…

@Marc -Devoteam- I agree. Even in Cloud, it’s often a good idea to first store the Value after fetching it and then use it in the post function.

Hello @Anubhav Agrawal That sounds very likely permission-related. Being able to edit a task does not automatically mean the user can also delete or archive it. Atlassian treats those as separate permissions, so someone may be able to update issues but still not see the delete/archive options. So I would first check: *…

@Anujah Siva You´re welcome :)

@Louise Henderson Good you can solve that. You can raise a Request to Atlassian and point onto that.

@Harshveer Kaur In your case i will look directly on provided Link from @Trudy P Claspill as she explained it there very Precise.