Bill Sheboy Expert

Hi @Elizabeth Thomas To do what you ask, I believe your rule would need to gather the issues in the sprint using JQL with a Lookup Issues action, and then use both smart value, list filtering to find the ones to link to the Test Plan. If I understand your structure (not the hierarchy), it is like this: * a Sprint…

You may not need the condition if you use the format() function, as that can return a quarter, such as Q1, Q2, Q3, or Q4 for a specific date. For example: {{issue.duedate.format("qqq")}} Please use a different format, based on the documentation, if that does not meet your needs. (e.g., including the year with the quarter) 

Would you please post an image of your complete rule, the action where the labels are added, and the audit log details? Those may provide context to explain what you are observing. Without seeing the rule, I suspect the cause is either in a condition or in the edit action adding the labels.

Hi @Katherine Chan To confirm my understanding of your terminology, what do you mean by "smart variable" and a "list of values"? Automation rules use smart values to access issue fields and other data available to the rules. For example, here are the ones for issue…

Thank you for clarifying! The built-in control chart can usually supply those values, but on a chart rather than on a report for further analysis (e.g., trends, variability, etc.). If you want to perform more analysis you would need one of these: * a marketplace addon for reporting or dashboard gadgets (as several of the…

Hi @Scott Federman Using automation rules requires learning and experimentation. I recommend trying to create this rule, and if you run into challenges the community can help. If you have already started a rule, please post an image of your complete automation rule, images of any relevant actions / conditions / branches,…

Hi @Sreelal CS Created variables are text strings and so they usually need to be converted to numbers for use in math expressions: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-text-fields/#asNumber For your example of a variable named "x" divided by a number custom field, customfield_34567:…

That rule uses a trigger of issue transitioned, from Awaiting Release to Live. How did the transition occur: did a person do it or did another rule perform the transition.

Going back to the beginning, you described adding a comment to Story A when the Due Date was changed in Story B to match. That expression I provided will provide the issue key for Story B for your comment. There was no other purpose for it, and so it is not used in the edit issue action.

Hi @David Law -- Welcome to the Atlassian Community! I recall from an earlier question an approach to solve this was to use the fieldChange smart values to build a dynamic JSON expression for the advanced edit, and perform all the adds and removes in one action. *…

Glad to help, and thanks for that link to the older post; I updated my answer to that one to simplify the approach in case people find it there. Happy holidays to you too!

Do you want to close this one out as "answered" to create another, or do you see it as part of the original question?

Hi @Banti -- Welcome to the Atlassian Community! What have you tried thus far to solve this scenario? If you have started a rule, 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…

Great; please change that condition from "issue type is not one of" to "issue type is one of" and re-test.

UPDATE -- here is a much easier way I found to do this, with no variables: Assuming the issues are in a lookup issues result, this can be done inline as follows: {{#lookupIssues.first.sprint}}{{#if(equals(state,"active"))}}{{name}}{{/}}{{/}} How this works: * assuming your lookup issues has JQL to find the issues in the…

Hi @David Alexander To do that inline, please try this expression with your lookup issues: {{#lookupIssues.first.sprint}}{{#if(equals(state,"active"))}}{{name}}{{/}}{{/}} How this works: * assuming your lookup issues has JQL to find the issues in the open sprint, such as with:* project = myProjectName AND sprint IN…

The way your condition is written, it will not update for those issue types. Do you want to invert that first condition, so it only updates if the issue type is Epic, Capability, Milestone, or PI Objective?

Using the how-to article linked below to find which smart values are supported by rules, I created a JPD multiple-select field with weighting: the weight values were not available to the rule. Only the selected values were available. https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/ I…

Well done! And I see why your JQL condition failed: there are embedded spaces (and other characters) in the values. The fix for that would be to wrap the smart value in quotation marks for the JQL, like this: Account = "{{issue.customfield_10044.value}}"

Thanks; that rules out a couple of possible causes. Let's now check if the Tempo documentation is correct... Automation rules do not support all possible fields. For example, some fields from marketplace apps are dynamic and may not be supported. Smart values are name, spacing, and case-sensitive. And often the smart value…

Based on the image shown, I expect that match() results in comma-separated values of the account ids as text. (I always write stuff like that to the audit log after the action to confirm it contains what I expected.) To use that as a list, split your variable with split(",") and iterate over it.

Ah, this is a JPD project and you are trying to access the "weight" value which (I believe) is dynamically calculated across selected values for a set. Is that correct?

If two or more rules have the same trigger (e.g., both on Issue Created) covering the same scope (e.g., one global and one project rule), I hypothesize the order of execution is unknown and it cannot be relied upon to order actions. If instead one rule does something (e.g., a rule action) that could trigger another rule,…

I do not have the Data Center version to test this. Would you please post your entire rule, the actions, and the audit log details. Perhaps that will show something. By the way...when I just checked the Server / Data Center documentation for smart values, I do not see the asNumber function…

Well done! One value of using that REST API call technique is it confirms automation rules support the field...Some custom fields are not supported and knowing that will save time while diagnosing rule problems.

Hi @Milagrosa Puig 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 the community to offer ideas.…

Hi @jnolan The built-in velocity report does not have filtering. It shows the 7 most recent sprints: https://support.atlassian.com/jira-software-cloud/docs/view-and-understand-the-velocity-chart/ What problem are you trying to solve by filtering the velocity report? That is, why do this? Knowing that may help the community…

Hi @Luã Prata -- Welcome to the Atlassian Community! That is not a built-in Jira field, and was likely added by a marketplace addon / app. Perhaps work with your Jira site admin to identify the addons and then contact the vendor to check their documentation. Kind regards, Bill

Hi @Amjad Syed -- Welcome to the Atlassian Community! First thing, I have not tried this with Jenkins, and so I am making a suggestion based on what I know of rule actions. You could try using the Send Web Request action to call the Jenkins REST API functions to trigger the build. Please look here to learn about calling a…

Hi @Anjana V K Yes, that can be done. The rule will need to a have multiple-project or global scope to work on both projects. Such rules are created from the global rules area; as you appear to be a site admin, you should be able to do that.…