Bill Sheboy Expert

Hi @Roberto Martignano This is a very old thread, and so I recommend creating a new question with the "Ask a question" button at the top of the page...perhaps including a link to this thread for context. When you create the new question, please include the following for context: * what problem your rule is trying to solve;…

Hi @Beatrice Daehler -- Welcome to the Atlassian Community! Here is the suggestion to make the Sprint goal visible again on the board. You may vote for / watch it to see progress: https://jira.atlassian.com/browse/JRACLOUD-93338 Kind regards, Bill

Hi @mmarkham First, this is an older thread and so I recommend creating a new question, perhaps including a link back to this one for context. Next, I believe there is no public REST API for Atlas (or Atlassian Home) goals yet, and so rules cannot support them with smart values. Here are the relevant suggestions if you…

Thanks for that information, please try the expression I suggested with the conversion before the max function: {{lookupIssues.customfield_10023.toDate.max.jiraDate}} And, some FYIs: * When writing values to the audit log, consider adding some reminder text as that will help identify what is being logged...particularly…

Hi @J D After the Create Work Item action, add a Branch to the most recently created work item, moving the transition inside that branch. Kind regards, Bill

Hi @Maxime Reynier -- Welcome to the Atlassian Community! Short answer: as this is a one-time need for the import, please ask your project admin to partner with the site admin to make the rule changes, and to disable the rule when done. Global and multiple-project scope rules are quite powerful and impactful. This is the…

Hi @Antonina Yudina In a single Create Work Item action, one cannot select both a specific field from the dropdown list and update it with JSON. Usually, this leads to strange rule errors, although it could also create an unpredictable update. The solution for your scenario is to first combine the Epic's values with the…

Hi @Anjali Behera -- Welcome to the Atlassian Community! Where are the relationships between possible assignees and their managers stored? For example, if they are stored as user, entity properties or as asset data, they could be looked up when the rule runs to notify the manager. However, if they are not stored anywhere,…

Hi @Rohini Chavan -- Welcome to the Atlassian Community! There is an active incident causing delays in rule execution. Please look / subscribe here to learn more and receive updates: https://jira-software.status.atlassian.com/ Kind regards, Bill

Hi @Travis Hill Please post images of: * your current, complete rule in one image, and * the complete Edit Work Item action. And just to confirm, that is the built-in Target End date, correct? If so, I believe the value is provided to rules as a text representation of the date, and so it needs to be converted to an actual…

Hi @Valerie -- Welcome to the Atlassian Community! Is that the built-in Target End field? If so, I believe that is provided to rules as a text representation of the date, and so the list max function cannot operate on it until the text is converted to a date. For example, please try this:…

Hi @Carolyn Hinkel Have you tried logging into JAC, the public backlog of suggestions and defects, to vote for it? Kind regards, Bill

Thanks for clarifying, @Kunal Dhir as I did not know if you needed the actual count or just the 0 indicator. (There are several related knowledgebase articles for setting such counts.) For the rule you show, the Scheduled Trigger use JQL to find issueType = Feature. But you describe Initiatives are the parent, so shouldn't…

Hi @Calvin This question is for the formula fields in Jira Product Discovery (JPD) and not for an automation rule. Kind regards, Bill

Hi @Kunal Dhir -- Welcome to the Atlassian Community! The article you linked to uses Epics and the built-in parent field for the relationship between children and their parent, Epic. You appear to be Premium license level, and so I wonder: did your site admin configure the hierarchy such that the parent / child…

I suspect it "worked" for the comment because the Due Date is one of the earliest fields supported by rules, and so has multiple different capitalizations versions. If you check the endpoint spec, it is "duedate". Now that we have excluded that as a cause... For the rule image you just posted, the smart value used in the…

Hi @Tayo -- Welcome to the Atlassian Community! I believe the Atlassian Intelligence (AI) features in Confluence are available in the Premium and Enterprise license levels: https://support.atlassian.com/cloud-automation/docs/actions-in-confluence-automation/#Atlassian-Intelligence--AI- Which license level are you using?…

Your Edit Work Item action has no value for the Due Date field, and so it is clearing it. And, the smart value for the Created Variable action is incorrect: the one for the Due Date field is duedate (i.e., smart values are case-sensitive). Rather than using the variable in the Edit Work Item action, please set the field to…

Hi @Debbie Heard Please try testing the internal smart value for the just-added comment: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/#--comment-- Kind regards, Bill

Hi @Bobby Moyini Your question indicates the work item you want to monitor is a Subtask. In that case, if the trigger work item is that Subtask, the rule should not branch to Subtasks, but instead just perform the condition check and send the message. Kind regards, Bill

I just tested this again with Jira Cloud and it worked as expected: with the generic Work Item Updated trigger and the Smart Values Condition, the rule only proceeded when the Rank changed. What action were you taking when the rule triggered? That is, what happened to the work item? There is a possibility the rule is…

First, please post an image of your updated, complete rule for context. Thanks! Next, by default the actions of one rule do not trigger other rules. This is to prevent accidental looping problems. When you intentionally want the actions of one rule to trigger others, in the downstream rule enable this option in the details…

Please try to stay within one thread when responding. That will help others reading this question in the future know if there are multiple possible solutions. Thank you! My suggestion was to store the {{branch}} smart value in a variable, but when you do so, it should not use the same name. For example: * action: create…

Hi @Anurag Vipin Vaidya Adding to the suggestions from @Evgenii ... Although automation rules can send emails when something causes an error, that will not indicate all possible automation problems: * a configuration change could alter the rule behavior, including by not limited to changes with: product licensing, users,…

Hi @Dhanapal Mohanasamy Thanks for the information and the work the team is doing on automation improvements! As this REST API seems related to this open suggestion, what progress can you share on endpoints to manage / monitor the automation audit logs: https://jira.atlassian.com/browse/AUTO-51 I have been experimenting…

Hi @Stewart_ Emily _ Global D_T When the rule uses Lookup Work Items on a multiple-selection, user field, that produces a list of lists. Thus when the distinct function is added, it is checking the sets of selections. For example, if you had four work items with these user selections: *…

Your original question seemed to be: GIVEN a rule with a Work Item Updated trigger WHEN a Work Item is transitioned to a new status THEN I do not want the rule to process I believe the possible cases are: * When only the status changes (e.g., by directly editing the Status from a single work item view), the rule should not…

You are correct on the trigger to use Work Item Updated when checking for a Rank change. I notice you are using a different smart value than what I tested. After a quick re-test I find: * {{changelog}} is the one used with that trigger and contains data for the changed field(s) * {{issue.changelog}} is an undocumented one,…

Hi @Rob Geritano Just following up to check if this answered your question. If so, please consider marking this one as "answered". That will help others with a similar need find solutions faster. If not, please let the community know what help you need with the rule changes. Thanks!

Hi @shriya Please post an images of the following to provide context for what you are observing: * your complete rule in a single image for continuity, * the action where you are using that smart value, and * the audit log details showing the rule execution. Until we see that... I recall some of the smart values (including…