Akash Singh Community Champion

@Petru Simion _Simitech Ltd__ Your app appears to be working fine on my end as well. Have you tried using a different browser to see if that makes any difference? Also, you might want to switch your network or enable a VPN and try accessing the app again. In my experience, some local ISPs fail to resolve the DNS for Forge…

@Nguyen Le Yeah, automatic resize doesn't work at all right now. You would be better off declaring a static size and work with it. You can track the progress on this bug here.

@Petru Simion _Simitech Ltd__ Apologies for overlooking that detail in your post. Could you let me know which template app you're using? I can try deploying and installing it on my end as well. Also, does it work only when the developer is tunneling, or does it run even without an active tunnel?

@Petru Simion _Simitech Ltd__ If your app is deployed in the Development environment (indicated by the "Dev" badge in its name), only users listed as Contributors in the Developer Console will have access to it. To allow broader access, you’ll need to deploy and install the app in the Production environment. Staging and…

@Sherwin Soriano If your goal is to run the automation only once, you can achieve this by using a Manual trigger in your automation rule. Here’s how: Set up the trigger: Choose Manual trigger from the "work item" as your trigger. You can also limit who can run the rule by restricting it to an admin group (see the…

@מיטל כגן Welcome to Atlassian community! Atlassian product licenses are assigned to individual users (named licenses), rather than being floating or shared as you suggested. This means you can grant product access to up to 25 users in your organization at any given time. If you attempt to assign a license to a 26th user,…

@Thushan Nirasha Welcome to Atlassian Community! The Jira backup API endpoint (/rest/backup/1/export/runbackup) is not part of Atlassian’s officially supported APIs, and currently, none of the classic scopes grant permission to perform this operation. For now, I recommend continuing to use this API with an encrypted…

@Anna Arczynska Since your organization does not use Atlassian Guard, I'm wondering if the user had enabled MFA through a third-party login provider (e.g., Microsoft or Google), or if they secured their account using Atlassian’s native 2FA—which, notably, cannot be enforced by admins without a Guard subscription. If MFA…

The roadmaps and hierarchy features look great, excited to get hands-on with them soon!

@Anna Arczynska Is your organization using Atlassian Guard? If so, you can request your organization admin to create a temporary authentication policy that bypasses SSO and disables MFA. You can refer to this article for more details:🔗 Edit authentication settings and members

@Angie Allen Yes, this is indeed achievable using a custom app built with Atlassian Forge, which is Atlassian’s cloud development platform designed to extend the functionality of Jira and other Atlassian products. To implement this, your team would need some familiarity with JavaScript and React, as Forge apps are…

@Alex Meyers Issue Key changes are included in the changelogs as well, see screenshot below for an example.

@LPK Your use case would ideally require a reduce-like function that can iterate over the lookupIssues list, filter issues by issueType, and aggregate the counts. However, such advanced list operations are not currently supported in Jira Automation smart values. As a workaround, I recommend breaking down your lookupIssues…

Count me in too!

@Alex Meyers Welcome to Atlassian Community! To fetch issue comments, you now need to query a separate resource endpoint: Issue Comments API – Jira REST v3 See curl command below for reference, curl --request GET \ --url 'https://your-domain.atlassian.net/rest/api/3/issue/{issueIdOrKey}/comment' \ --user…

Hi @Aravindh P, You would first need to create a Field value changed trigger and start looking out for any changes to Assignee field and use below template for Send email action. To: Assignee (from dropdown) CC: {{initiator.emailAddress}} (smartvalue) Hello, The assignee for issue {{issue.key}} ({{issue.summary}}) has been…

@Jamiu Adeleke Welcome to Atlassian Community! API tokens with specific scopes are tied to OAuth 2.0 (3LO) and cannot be used directly with standard Jira REST API endpoints. To use OAuth 2.0 tokens, you'll first need to construct the request using the appropriate resource URL that includes your Cloud ID, as outlined in the…

@Jane Brusilovsky Just to add to my earlier response, API tokens with specific scopes are tied to OAuth 2.0 (3LO) and cannot be used directly with standard Jira REST API endpoints. To use OAuth 2.0 tokens, you'll first need to construct the request using the appropriate resource URL that includes your Cloud ID, as outlined…

Hi @Jane Brusilovsky, Welcome to Atlassian Community! To create a Work Item (previously referred to as an "Issue") in Jira Cloud using the REST API, you’ll need to interact with the Create Issue endpoint: POST /rest/api/3/issue 📘 API Documentation – Create Issue ✅ Minimum Required Fields For the issue creation to succeed,…

@Andy Macourek Thank you for sharing the field details. It appears you're trying to populate the "Affected Services" field in your issue and are looking to retrieve a list of all available Services in your instance. At this time, there is no public REST API available to fetch this information. However, Atlassian has an…

@Andy Macourek If your objective is to create issues programmatically, you should use the Issue Create Metadata API to retrieve all available fields along with their allowed options. Currently, you're using the editmeta resource, which only provides information about fields available after an issue has been created. To get…

@Hiroshi Kuramochi I am glad that I was able to solve your problem. Could you please mark my answer as accepted? This would also help others in the community who might face a similar situation in the future.

@Hiroshi Kuramochi Welcome to Atlassian Community! It looks like you're trying to assign a Team to the Work Items (previously known as Issues) in your plan. To do this, first add the Team (チーム) field to your plan by clicking the Add Field (フィールドの追加) button in the table header. Once added, you’ll be able to select the…

@Nur Fatin Yes, correct. You would be better off asking your Jira Site Admin to create new multi-user picker field at global level for your requirement.

@Terry Thomas You could try Auto-Schedule your plan work items and overwrite all values with the Sprint, see screenshot below. Read more about how auto-scheduler works here: https://support.atlassian.com/jira-software-cloud/docs/how-does-the-auto-scheduler-in-advanced-roadmaps-work/

@Nur Fatin In the screenshot you shared, the log action doesn’t display any email addresses for the fields, which indicates one of two possible scenarios: a. Both fields might be empty for the Work Item, so no email address was found.b. The fields are populated, but the user objects don’t include the emailAddress…

@freya If that resolves your query, could you please mark my answer as accepted? This would also help others in the community who might face a similar situation in the future.

@Qin Han Is it a Team managed or Company managed project where the automation is executed? What is the field type of customfield_11542, is it a single or multi user picker field?

@freya Welcome to Atlassian Community! Is it a Company managed or Team managed project? If it is a company managed project, then could you please confirm if Component is correctly added to Issue Create/Edit screens for the Work Item type (formerly knowns as Issue Type) in the project? Additionally, is this behavior just…

@Nur Fatin After reading through @Bill Sheboy’s response, I realized that simply replacing the semicolon with a comma in my original post should allow your automation to work without requiring branching. Additionally, I noticed that we had been using the wrong custom field ID for those fields. With the correct IDs, the…