Akash Singh Community Champion

@Nur Fatin Apologies for the confusion, I initially assumed that colon-separated emails within a smart value would be accepted in the To field of the Send email action. However, it turns out that when using a smart value, the To field expects a single email address. That said, there's still a way to achieve the desired…

@Nur Fatin This seems to be correct, can you add a log action and check the value stored in the variable?

@Nur Fatin You're were on the right track, since this is a multi-user picker field, directly referencing the email address using {{issue.customfield_11517.emailAddress}} won't work as expected. The field contains an array of user objects, so you'll need to iterate over that array and extract the emailAddress from each…

@Sreenivasaraju P If the custom field and its context are predefined and not expected to change per request, you can add a new option using Jira’s API for creating custom field options. You can refer to the official documentation here. To automate this, use the Send web request action in Jira Automation to trigger the API…

@Lalith Motay Could you share a screenshot of your automation configuration? Have you defined this JSON in additional fields section when creating the issue or in an Edit issue action once they are created? As the error message suggest, these fields are mandatory and would need to be set while creating the issue.

@Lalith Motay 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.

@Lalith Motay I’m assuming that 17780 and 17781 are the field IDs for the Target start and Target end fields in your instance. If that's correct, here is the JSON you should use: { "fields": { "customfield_17780": "{{triggerIssue.customfield_17780}}", "customfield_17781": "{{triggerIssue.customfield_17781}}" } }

@Lalith Motay In that case, you can fetch the dates from its parent and store it in a variable. You can then reference that variable using the smart value in the json.

Hi @Lalith Motay It seems you're trying to modify the Target start and Target end date fields, which are part of Advanced Roadmaps/Plans. Since these fields are system fields introduced by Plans (previously a separate plugin), they aren't directly supported by Jira Automation. However, you can still edit them using the…

@Susan Chin Welcome to Atlassian Community! The quickest way to resolve this is by reaching out directly to Atlassian Support. They have a process in place for these situations and can assist with updating the billing contact and adding new admins. You can submit a request here: Atlassian Support I've also requested…

@Jason Cookman, Welcome to the Atlassian Community! It looks like your backend code is directly throwing an error, expecting the frontend to catch and display the error message. However, since your backend runs in a serverless environment, this approach isn't ideal. Instead, you should return a structured response…

@Mansi Gusain You can use the issue search API resource to find issues using JQL. Refer to the documentation for more details. To search for child issues, you can use the following JQL: parent = MG-662 As a result, your API request might look like this: https:/mysite.atlassian.net/rest/api/3/search/jql?jql=parent=MG-662

Hi @Jedsada R_ As @Trudy P Claspill mentioned in his response, your automation rule checks whether the issue has any linked issues with the link type "Blocks." If such issues are found, the rule attempts to transition the triggering issue to "In Progress" instead of updating the linked issues. To transition the linked…

@Neill B Have you tested whether the issue occurs in the Chrome browser as well? Also, could you check the browser's developer console for any errors related to network requests? I guess that the workflow transition has an issue transition screen which is not loading in the browser, I encountered a similar issue sometime…

@Mike Chapman Welcome to Atlassian Community! I recommend using Basic authentication with your email as the username and an API token as the password, rather than passing the API token in the header. Check out my answer on this post and follow the steps outlined—you should be able to fetch data from Jira without any issues.

@Jamie Edmondson Does your organization use Atlassian Guard (formerly Atlassian Access)? * If yes, you can find detailed logs of user management events and more in its Audit Log. Check out what activities are tracked in Atlassian Guard’s audit log here. To view and search your organization's audit log: * Go to Atlassian…

@Vishnu Vardhan Chenna Try using the below Smart value, this should work for sure. Use month format to only get the number value and use less than equal to function (lte) for comparisson. {{#if(now.format("M").asNumber.lte(3))}} {{now.minusYears(1).format("yyyy")}}-{{now.format("yy")}} {{/}}

@Murali K R Welcome to Atlassian Community! You’re on the right track! Below are the steps to set up a live Excel dashboard that automatically fetches Jira issue data — ideal for creating a burndown chart. Prerequisites Before starting, make sure you have: A Jira API Token — You can create one by navigating to:Manage…

@Deepak Welcome to Atlassian Community! When you create a variable in Jira Automation, you can reference and use that variable later in your rule using smart values. For example let’s say you create a variable called myVariable and set it to value from a Priority field. You can then use it in fields like Summary,…

@colicelab Welcome to Atlassian Community! Check out my response on this post for steps to revert to the old navigation experience. Keep in mind that while you may be able to switch back to the old view for now, the new navigation is here to stay. At some point, the option to revert may no longer be available.

@Amruta Harale Try converting the date to the format 23/Mar/25 12:00 AM, replacing any dashes with slashes and changing month to it short month name like Mar or Apr.

@Joseph Ranjan You can use GET /rest/api/3/webhook to fetch all the registered dynamic webhooks for the calling app. Your php code to register the webhook does seem to be correct, you can also check if the webhook had any failed deliveries in last 72 hours using the this endpoint GET /rest/api/3/webhook/failed Also, please…

@Joseph Ranjan 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.

@Alok Kumar Welcome to Atlassian Community! Atlassian is rolling out a new navigation experience in Jira Cloud to enhance usability. Learn more about what’s changing here. Your site might have received this update already, if you wish to go back to the old navigation experience follow the steps below. * From the top right…

@Ankit kharola Please refrain from posting confidential information such as API tokens on community posts. I have omitted the token from your reply and modified your answer for now. To answer your question, please make sure manage:jira-project classic scope is present in your app manifest as it is needed for the endpoint.

@Ankit kharola 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.

@Ankit kharola In that case, it would be best to use the endpoint I shared in my previous response.

@Ankit kharola After thoroughly reviewing the API documentation, I found that this endpoint only returns workflow transition rules that were created by the calling app itself. It does not return any rules created directly by admins through the Jira product UI. Could you please confirm if there are any workflows in your…

@Joseph Ranjan Welcome to Atlassian Community, Your app is registering a dynamic webhook using this endpoint. Dynamic Webhooks once registered are specific to your app only, they are not related to admin webhooks that you see under Settings section. Read more about registering webhooks here. The document also suggest that…

@Ankit kharola It seems you are trying to fetch this data in your Forge application. Could you please share the output for the below statement, console.log(types, "types"); Also, the REST endpoint used in your code requires the manage:jira-configuration classic scope for the app. Could you please check your manifest.yml…