Bill Sheboy Expert

Hi @Krishnadhas N K Yes, and...to John's suggestion, you may use this REST API function with the JQL: https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-search/#api-rest-api-3-search-get Please see the details for managing the returned issues, fields, etc. Kind regards, Bill

Please post images of the audit log details showing the rule execution and of the Edit Issue action. You described wanting to sum the values in the Technical Task issues which are children of the Product Story issue... * The JQL condition seem incorrect as that will not test if the trigger issue is a Technical Task * And,…

Hi @Amzad Khan With the built-in dashboard gadget, the closest you can do is to Sort by Total with a direction of Descending. If you need more flexible reporting, please check the Atlassian Marketplace for addons / apps: https://marketplace.atlassian.com/ Kind regards, Bill

Hi @Mads Aagaard Andersen I do not believe that is possible with automation rules. There is no REST API function or automation rule action to add / manage the shortcuts for Jira Work Management (JWM) projects yet. Kind regards, Bill

Hi @shelleyc Comparing what you show, your smart value expression does not match the spreadsheet formula: the first part is missing the outer MAX(0, ...) before performing the subtraction. I also recommend writing each part to the audit log in your rule and comparing that to the spreadsheet results. That may clarify where…

Hi @Raven Clarke -- Welcome to the Atlassian Community! When you only have the accountId value from a mention, the other user data is not available for use: displayName, emailAddress, etc. A few possible workarounds are: * use the Send Web Request action to call the REST API to search for the user by their accountId, and…

When releasing the version with the dialog and selecting "Move unresolved issues to..." another version, that removed the released-version value from the Fix Version field. Once the rule triggers, only the "fixed" / completed issues can be branched over in the rule. I recall from a different community question that using…

Hi @Syd Heller The "matching JQL" for that Related Issues condition must be well-formed JQL. That is... <some_Jira_field> <some_operator> <some_value> ...and so on {{issue.resolution}} cannot be on the left-hand side of the JQL as that would try to compare a value to another value. Please try this instead: resolution IS…

Hi @Jill Vieregge To access the child of the cascading field, please try this: {{issue.customfield_12330.child.value}} And FYI...to learn about the content and structure of smart values available for an issue, this how-to article can help. The idea is to call the REST API function with a browser tab to query the issue with…

Hi @Iñigo Ruiz To do this with one rule...after the issue is created, the rule could use the Send Web Request action to call the REST API function to transition the issue, passing the {{createdIssue.key}} and the correct transition id for the workflow. As a disclaimer, I have not tried this approach in a rule before.…

Hi @Jayesh -- Welcome to the Atlassian Community! For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected. Those will provide context for…

Hi @Joshua Dickerson First thing, as this is an older thread it is often better to create a new question and link back to the older ones. That ensures the maximum number of people see it to offer suggestions. Otherwise, only people following the older threads see it. Back to your questions... You do not describe what are…

Would you please compare what you are seeing to the images @Earl McCutcheon posted, showing the "X" at the right side of the parent field? If you see something different, please post an image of an example Bug including the parent field. Selecting that "X" should remove the Epic connection to the Bug.

Awesome; I am glad to learn that helped!

I believe you need the id for a Team field type, and the value must be in quotation marks. Please try this: { "fields": { "Team": "{{triggerIssue.customfield_10001.id}}" } } If that does not work, please post an image of the error from the audit log details.

What do you want to do if there is no parent issue? For example, if there are no changes to that field, you may add a condition to prevent further processing: * trigger: issue created * action: re-fetch issue * smart value condition: * first value: {{triggerIssue.parent}} * condition: does not equal * second value: leave…

Sorry, I do not know that. You could experiment with a Jira site webhook on "attachment created" and intercept that with a webhook trigger. That should confirm if attachment added on the workflow screen sends the event. To try this, create the rule first to get the webhook URL and then use that when setting up the site…

With the version-related triggers, the rule may then branch over "issues in version". Then use rule conditions for your test and actions for the version changes. I suspect you may need to use advanced edit with JSON and text functions to specifically remove the version from the field.

For Jira Cloud, the one way I know how to do this is: merge the versions to a known delimited-format, split / distinct, and parse with match(). For example: * for all the issues, merge together all of the fix version data in a delimited, created variable* name: varAllFixVersions * smart value: {{#issues.fixVersions}}…

First, your trigger is on the "Release Sprint" field and so that is the only one available with the changelog within the rule. The "Pushed Sprints" field did not change. Next, please confirm you have the correct smart value for your field in the condition... Smart values are name, spacing, and case sensitive, and they may…

No, the reverse of that: for a date / time value convert to your time zone before using the plusBusinessHours() function.

Yes, that helps: your quarters are shifted, such as for a financial planning year. I do not believe there are built-in rule functions to change when the calendar year starts for quarters. To do that for your scenario, you could use date functions to perform math, shifting the date, and then formatting as quarters.…

Thanks for that information. I recommend first checking if the Team field is available in the fields dropdown for the Issue Edit action. If it is, remove the JSON and select Copy from Trigger Issue for the field. If the Team field is not in the dropdown, the advanced edit with JSON is required. You should only specify one…

Hi @Lucas Ferreira Short answer: no, there are not. You could create a filter for the issues in the open (current) sprint and another adding the status to show in two filter gadgets. You could also check the Atlassian Marketplace for addon dashboard gadgets, as there are several which can display number counts like that.…

Hi @Mari-Ann Eriksen Yes, and...to the suggestions from Nick and Gary: How do you want to use the People field later in automation rules? I recall team-managed project (TMP), People fields have limited data within rules. And JPD projects seem based upon TMP. For example, People fields cannot be used in rules to send…

Hi @Alain BEAULIEU Based on my understanding, anywhere in the Jira UX where you can "release" a version is going to show that dialog box, and that seems it would be too late for what you want to do. Instead you may need to create a rule, perhaps manually triggered from an example issue or scheduled, that would update the…

Hi @Markus Hoofe -- Welcome to the Atlassian Community! Short answer: Your workaround looks like a good approach. More information... The changelog entries do not work for that trigger, Version Updated. And even if they did, there are multiple events which can fire that trigger for rules...and some version updates which do…

Hi @X2EVWHAL -- Welcome to the Atlassian Community! I am unclear what you are trying to accomplish as your rule: * Uses advanced edit with JSON to repeatedly set the Team field to different values. I believe only one value should be passed when setting the Team. * Same thing as above, except editing the trigger issue. What…

Hi @Dimitri Cools Short answer: For this scenario, I recommend using a Lookup Issues action with JQL and the linkedIssues() function for the specify link type to find the issues, then get the keys from the lookup result: https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Lookup-issues…

Hi @Selva Praveen Elango JQL is an issue search language. It does not have any aggregation features, such as with a SQL. To do what you ask you could consider: * do not include the subtasks' original estimates in your reporting; only report at the story level * investigate how you sum the original estimate values for the…