Utkarsh Agarwal Community Champion

Hi @Laurence Oldfield Welcome to the community! With an Atlassian Guard subscription, you can create a non-billable policy when you don’t want to pay for certain users. Refer: https://support.atlassian.com/security-and-access-policies/docs/what-is-a-non-billable-policy/ Kind Regards Utkarsh

Hi @Alexandre Luy Welcome to the community! The behavior was reported earlier in a Jira Cloud bug (JRACLOUD-87335), but it was closed without a fix due to low activity. Since there’s no active ticket for this specific backlog behavior now, I recommend raising a new suggestion on https://support.atlassian.com/contact/ . If…

Sorry, but these are not AI-generated; these are based on my experiences. 

Hi @Prasad Bonthu This is an interesting case, and based on similar scenarios I’ve encountered, here are some possible causes and investigation steps: Possible Reasons for the Duplicate ("Ghost") Account * Migration Artifacts – If your instance underwent an on-prem to cloud or cloud-to-cloud migration, a user might have…

Thanks for sharing the details! A couple of things to check: * Confirm the Automation Actor Make sure the rule actor (e.g., Automation for Jira) is added to the same project role whose ID you used in jira.permission.edit.projectrole. You can verify this under Project settings → People. * Using a Group Instead Did you try:…

Hi @PLaksh11 When Jira issues are set to read-only via workflow properties (like jira.issue.editable = false), automation rules can't update them. The simplest practical workaround is: Grant edit permissions specifically to your automation user or group even in the read-only status. To achieve this: * Go to your workflow…

Happy Jira Admin Day! 🎉 Huge thanks to all the incredible Jira admins out there for keeping our teams productive, organized, and stress-free. Your behind-the-scenes magic makes all the difference! This year, our big win was successfully migrating a large-scale, complex Jira instance from Server to Cloud, with zero…

Hi @川目 沙英 Your existing rule for closing alerts only listens to the issue_updated event, which explains why some alerts aren't closing. Recommended solution: Adjust your existing "Close Alert" sync rule to listen to additional events that might trigger alert closures. Specifically, update the rule condition to: IF: status…

Hi @Andrew Fernando Welcome to the community! Advanced Roadmaps doesn't offer a direct setting to customize the weekday for projected sprint start dates—they automatically start right after your team's last defined sprint ends. To align your projected sprints (and thus capacity planning) with your team's Wednesday start: *…

Hi @Sean Loh Welcome to the community! This has been asked multiple times, please refer post below which has references: https://community.atlassian.com/forums/Automation-questions/How-to-update-story-points-for-an-Epic-when-one-of-the-child/qaq-p/2526082 Kind Regards Utkarsh

Loved revisiting the core values of the community—‘Be Real’ really stood out to me. A great reminder that authenticity builds better collaboration!

Hi @Keisha Phoenixx Welcome to the community! To make Features the parent of Stories, you’ll need to adjust the issue type hierarchy under Jira Settings > Issues > Issue Hierarchy. This feature is only available on Jira Software Premium and Enterprise plans, as it uses Advanced Roadmaps. Currently, it looks like you’ve set…

Hi @TechComp Jira Data Center does not emit any event on component creation, as components are part of project configuration. This means neither Jira automation nor ScriptRunner listeners can detect when a new component is created. To replicate issues from an existing component (e.g., Finance 2024) to a newly created one…

Great tips! Starting simple and iterating really makes a difference when building AI agents.

Hi @Jonnie Bloor Welcome to the community! You can do the following: * Trigger:* Use "Issue transitioned" * Configure it for transition to status category Done * Condition:* Add "Issue fields condition" * Check that “Parent” matches a specific issue key (e.g., ABC-123) (Alternatively, use labels or custom fields on the…

Hi @Vicky Pagnaer In my opinion, the best approach is to copy the workflow, edit it to delete the global transition, add your new one, and then assign the updated workflow back to your project. This avoids impacting other projects using the same workflow. Regards Utkarsh

Hi @Kevin Jay Welcome to the community! Yes, the Atlassian MCP (Model Context Protocol) server can allow Claude to read or download attachments (like images) from Jira issues, provided proper access is granted. To enable this: * Claude must be connected via the Atlassian Remote MCP server. * The authenticated user (via…

Hi @Petru Simion _Simitech Ltd__ In Cloud, post-functions run via the ScriptRunner app user context (not the user who triggered the transition), so Users.getLoggedInUser() (or getLoggedInUser() in Groovy) will return the ScriptRunner add-on account. If you need to run actions as the real user, update the post-function…

Hi @Ritika Ojha Yes, this is possible using Jira Automation. You can set up two separate rules: * Label issues created in a specific project* Trigger: Issue Created * Condition (if using global rule): Project = TSM1 * Action: Edit issue → Labels → Add tsm1 * Label issues linked to a specific project* Trigger: Issue Linked…

Hi @Guilherme Rocha This is actually expected behavior in JSM Cloud. The resolution screen uses a simplified editor, and unfortunately canned responses aren’t supported there yet. Atlassian has an open feature request for this, refer: * https://jira.atlassian.com/browse/JSDCLOUD-12765 *…

Hi @Lelani Mayer This sounds like a performance limitation rather than an actual issue with the filter itself. While 437 issues isn’t typically a problem, the number of fixVersion values being queried — especially across multiple projects — can increase the complexity of the JQL and the load on the UI/export functions.…

Hi @Adrien Lesueur Welcome to the community. If you’re unable to assign issues to Adrien, it’s likely due to missing permissions or application access. Since these settings are managed at the project or site level, you'll need to contact your project admin or site/org admin to: * Ensure Adrien has application access to…

Hi @Katrin Erhardt If you're not seeing the custom filter under “View all filters,” it’s likely tied to the board and hasn't been shared with you. Each board is backed by a saved filter, but it won’t appear under “View all filters” unless: * You have permission to view it (i.e. it’s shared with you), and * It's not a…

Hi @Knox McCormac You can’t capture audit logs per site individually, but at the Atlassian Organization level, you can set up audit log webhooks to stream events from all sites linked to the Org. Refer to: * Audit log webhook setup * Track organization activities Once configured, you can filter events by product or siteId…

Hi @Praveen Users can't access Jira via SSO due to mismatched usernames or misconfigured SAML attributes. Ensure the IdP sends the correct NameID, users exist in Jira, and attribute mappings are correctly set (e.g., ${NameID} for SSO plugin v4.1+). Also, verify base URL and proxy settings.

Definitely more control and governance

Hi When you remove an org admin in Atlassian Cloud, the audit log entry typically appears as: Removed user from group org-admins This is because org admin privileges are granted through membership in the org-admins group. So, whether you remove a user from this group directly or via the dedicated Administrators section in…

Hi @Vidya VASUDEVAN This error typically occurs when the project key 'DTE' doesn't match any existing project in your Jira instance or if you don't have the necessary permissions to access the project. Here’s how to troubleshoot and resolve this issue as a Jira admin in Jira SaaS: Steps to Resolve: * Verify the Project…

* Trigger: Set to run weekly (e.g., every Monday morning). * Condition: Use JQL assignee IS NOT EMPTY AND created >= startOfWeek() AND created <= endOfWeek(). * Branching: For each assignee, count the number of tickets. * Action: If the count exceeds five, trigger an email or notification to the assignee or a manager.

Hi @Peter van Wonderen Welcome to the community! It sounds like there’s some confusion between the site URL domain (e.g., yourcompany.atlassian.net) and the email domain (e.g., @yourcompany.com). To enable 2FA using Atlassian Access, you need to verify your email domain, not the Atlassian site URL domain. Let me break this…