Bill Sheboy Expert

That technique, also described here with the automation documentation, is quite valuable when working on rules. Smart values are name, spacing, and case-sensitive, often do not match the displayed name on the issue views, and the structure within the data is important as well. Using the REST API function will help both…

Awesome; I am glad to learn that helped! I like that that technique of outputting the whole changelog, yet it may not always work. When an object is just written to the log / used, sometimes it only returns the default attribute. For example, writing {{issue}} normally only returns the key. As rule behaviors like that are…

The {{sprint}} smart value is only available with the sprint-related triggers. This is one reason I was asking about seeing your complete rule. If the trigger is instead Issue Created, the smart value {{sprint}} is not available. Instead it is {{issue.sprint}} ...again depending upon the context within a specific rule. If…

Hi @Mark Haller Here is the documentation on conditional, smart value expressions to get you started: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-conditional-logic/ Another key thing is the smart values...they are name, spacing, and case-sensitive. And, a field's smart value may not match the…

Hi @Andras M 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 @Ryan Ruhland There are occasionally problems with the changelog for list fields (like multiple select users), and so please try this to confirm it works... When the rule trigger is Value Changes for your field, this smart value will contain the added and deleted values, respectively: {{addedFieldChange.values}}…

Please remove the extra spaces or the smart value expression will not work: {{lookupIssues.Story points.sum|0}}

Hi @Gary Dlugy That is a known problem with the defaults for a product where customers cannot adjust them, and it was certainly made more visible when JPD was added...as it has a different licensing model than Jira. You appear to be the site admin for a paid license, and so you can contact Atlassian Support here, and ask…

Hi @christopher.branaman Adding to Trudy's suggestions... I see several errors in the rule image you posted, with invalid smart values: case and typos. Smart values are name, spacing, and case-sensitive. When an invalid one is used, the rule uses null, and that often fails silently (with no error in the log). The smart…

Hi @Brett Andrews -- Welcome to the Atlassian Community! Adding to the suggestions from Laurie... Are you trying to perform one or both different updates in one rule or multiple rules? * When the Due Date or Start Date change for a Sub-task, update the parent issue (e.g., Task) to have the minimum Start Date and the…

Hi @Alicia Morgan Using automation rules successfully requires learning and experimentation. Rather than asking for screen images of a completed rule, I recommend trying to build the rule first. And if you run into challenges, post images of your rule and describe what is not working as you expect to ask for help.…

I was asking to see your complete automation rule, for context. Not just the smart value expression you are trying. It is possible the result is null or empty because of the way the expression is used. Seeing the entire rule and audit log details will help to clarify that. When posting the audit log details, please show…

I am glad to learn that helped. Please consider marking this question as "answered"; that will help others in the community with similar needs find solutions faster. Thanks!

Thanks for that information. Then my original suggestion still works: using the text function match() with a regular expression pull out the issue keys, and then iterate over those with an advanced branch to make your updates.

Are you trying to sum the story points for the issues with a specific label, or list the individual story point values for issues which have the specific label?

No, that is not possible. The drag-and-drop (to change issue ranking) only works when the board filter's is only sorted by ORDER BY Rank ASC As a work-around, you could add quick-filters by priority values and select the ones you are interested in viewing.

If you are using Jira Cloud, that should be the correct smart value but it appears to be empty. So step one: do those issues have a value in the Due Date field? If not, that is the problem. If you instead are using that custom field you mentioned, please let me know exactly which fields your calculation is using. Then we…

Hi @Francisco Duarte -- Welcome to the Atlassian Community! The built-in JQL can filter for a list of issues. It cannot list the history of issue status changes. To do that you could try the built-in control chart report, as described…

Hi @Ayşenur Şen -- Welcome to the Atlassian Community! Here is the defect for this, which you may watch / vote for to see progress: https://jira.atlassian.com/browse/JRACLOUD-82482 There is a noted work-around to use the bulk-update feature, from an issue search, to add a new Component...at least until this one is fixed.…

Thanks for the information, @Jimmy Seddon ! As a yes, and to trying out Jira Product Discovery, I suggest people read this article on the product transition from Beta to general release. The licensing and user configuration is different than Jira, and so understanding how to configure usage is valuable to avoid…

Hi @Valerie Knapp First thing, congrats on reaching that level of engagement and the continuing support I see you providing the community by answering questions well. I truly thank you! And I understand your concerns; it is unclear to me what behaviors the current system is trying to foster. (I am reminded of a quote from…

Hi @Shasheekant Patel What have you tried thus far to solve this problem? 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 not working as expected.…

Hi @Yulia Zhyliaieva What are the types of those fields? If they are numbers, you may used them directly with either of these methods: {{#=}{{issue.Impact}} * {{issue.Effort}}{{/}} {{issue.Impact.multiply(issue.Effort)}} The .value is only needed if the fields are selection fields. Kind regards, Bill

Hi @nasiruddin.nordin Context is important for understanding problems with automation rules. 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…

Hi @Laura Merino Diez If you do not have a marketplace addon / app for performing this type on analysis, you could try iteratively using Atlassian's interpretation of a control chart: https://support.atlassian.com/jira-software-cloud/docs/view-and-understand-the-control-chart/ Perhaps trying these steps: * Identify the…

Hi @Wendy Grapentine -- Welcome to the Atlassian Community! What problem are you trying to solve by doing this? That is, "why do this"? The issue history already contains this information about the field changes. Back to your question... What have you tried thus far to solve this? If you have a rule started, please post an…

As noted repeatedly, that is not possible with rule iterators. The rule could get close to that format using an HTML table. It could get closer still by adding a custom field to assist in sorting the epics and their child issues together. And please note: lookup issues is limited to 100 issues. If your expect your JQL to…

Awesome; I am glad to learn that helped!

Hi @April Chi Rather than the "collapse" option you show, where is the option to disable the display of sub-tasks in the backlog completely, for a project or an entire Jira site? If there is no such option, why not? Kind regards, Bill

Where is that log action: inside the branch? Have you checked if there are any leading / trailing spaces around the return from the table get() results? You could add a trim() to confirm that is not the problem. UPDATED: I forgot that I had figured out this scenario before :^) The rule editor for the JSON edit tries to…