Bill Sheboy Expert

Would you please post an image of your complete rule, images of the relevant actions, and the audit log details showing the execution? Those may provide more context to explain this symptom.

The date / time diff() function's units of measure are for date / time field differences. They cannot operate on arbitrary number values, as created by that article's suggestions. And so prettyPrint cannot work on just a number. If you expect issues to only be in a status / column one time, try using just the diff on the…

Thanks for that information. Please see the two possible solutions I noted earlier, try one of them and re-test.

Hi @James Smith Without seeing your entire rule for context, the most likely cause is the smart value for your custom field is incorrect. When the wrong one is used, it can silently collapse to null in rules without any errors shown. Smart values are name, spacing, and case-sensitive. And often the smart value does not…

If the issues and label values need to be manually audited (i.e., cannot be programmatically set / verified) you may want to try this: * create some saved JQL filters to return the issues of interest * create a dashboard to show the issues and their labels At the verification points, the team can use the dashboard to find…

For this type of summation, I recommend 2 rules: * triggered on story changes, update the parent epic * triggered on epic changes, update the parent initiative To make this work, the actions of the first rule will update an epic, and we want that to then trigger the second rule. By default, rules triggering other rules is…

For your first question, I believe you will need to conditionally set the sprint either to the from value or to null. If that does not work, let me know so I can experiment a bit. For your second question, date fields are usually stored as numbers, and so the mathematical operators for gte() and lte() should…

Hi @Ines B I am using Jira Cloud, and so cannot validate my suggestion for Jira Data Center's version of automation rules... Data Center does have the lookup issues action (with a limited number of fields) but does not have advanced branching, to allow iterating over things other than issues (e.g., assignee users). Here is…

Hi @pmitchell -- Welcome to the Atlassian Community! Based on the status of the suggestion I linked-to, there has been no progress on changing this behavior. IMHO...it seems like many of the recent design decisions target mobile / tablet break points rather than customers using monitors. Kind regards, Bill

Hi @Purni As this is an older thread, I recommend creating a new question and perhaps linking to this one. That will ensure a larger number of people see it to offer suggestions. When you create your question, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an…

Hi @Rachana Kandlagunta -- 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…

Yes, that is what I meant for a test with a known Slack ID value, Andrew. That would confirm a single, direct message works.

One adjustment you may want to consider: The issue created trigger can fire so quickly that some of the issue data may not yet be available to the rule...potentially leading to the condition not working as you expect. The work-around for this is to always add the Re-fetch Issue action immediately after the Issue Created…

Hi @krunoslav_majer Just following up to ask if you learned an answer from Atlassian support yet. Thanks! Kind regards, Bill

Hi @Ralston Africa Just following up to ask if the suggested answer solved your question. If so, please consider marking this one as answered to help others find solutions to similar needs faster. Thanks! If not...please describe what is not working as expected, and post an image of your complete current rule and of the…

Hi @Ezgi Just following up to ask if the suggested answer solved your question. If so, please consider marking this one as answered to help others find solutions to similar needs faster. Thanks! If not... From what you described, I believe you will need a multiple-project scope rule (stored with the global rules). To…

Hi @Gil Just following up to ask if the suggested answers solved your question. If so, please consider marking this one as answered to help others find solutions to similar needs faster. Thanks! If not, what is not working as expected? If the email is still not being sent for the rule you showed, some of the possible…

Hi @Jouni Riimala Just following up to ask if the suggested answers solved your question. If so, please consider marking this one as answered to help others find solutions to similar needs faster. Thanks! If not, please explain what is not working as you expected, and post images of your complete rule, the details of the…

Hi @Just Oudhuis -- Welcome to the Atlassian Community! Just following up to ask if the suggested answer solved your question. If so, please consider marking this one as answered to help others find solutions to similar needs faster. Thanks! Kind regards, Bill

Hi @Nils Hornitschek That cannot be done with an automation rule (and you have posted this question in the automation area). Instead please consider using a workflow validator for the field: https://support.atlassian.com/jira-cloud-administration/docs/configure-advanced-issue-workflows/#Validators Kind regards, Bill

I am glad to learn that helped. Please consider marking this one as answered to help others find solutions to similar needs faster. Thanks!

Hi @Irina Harutiunian Just following up to ask if the suggested answer solved your question. If so, please consider marking this one as answered to help others find solutions to similar needs faster. Thanks! Kind regards, Bill

Hi @Austin Mierow What do these labels represent for the different issues? That is, what problem do they solve? Knowing this may help the community to offer better suggestions. Until we know that... Is the assignment (or removal) of labels predictable based on information in the issue fields? If so, perhaps an automation…

Hi @Carla Ann Rowland My understanding is the REST API functions support adding one link at the same time as issue create, but my testing showed that not to be the case with automation rules: issues must be created and links added afterwards. It may be possible to add the links in the same rule...depending upon your rule…

Thanks for the topic and sharing your example, @Nikki Zavadska _Appfire_ Your board reminds me of many of the physical and Miro board retros I have used, including Sailboat. As a facilitator and participant in retrospectives since the early 80s, I have used lots of different methods, some better and some worser ;^) With my…

Hi @Regina -- Welcome to the Atlassian Community! Adding to Jack's answer... An adjustment to the suggested rule is to specifically use the Sprint which started the trigger, rather than values from the issues: * {{sprint.startDate}} instead of {{issue.sprint.startDate}} * {{sprint.endDate}} instead of…

Hi @Casey Meyer Adding to Walter's answer... There is already a suggestion to improve color selection after that change. You may vote for / watch it to see progress: https://jira.atlassian.com/browse/JSWCLOUD-26300 Kind regards, Bill

No worries; we are all learning, all of the time :^)

Hi @Moritz Spiller What is the purpose of your "project overview" board? If it is to view the status of issues across multiple projects and boards, cloning is not necessary. (Indeed, cloning creates the synchronization and other problems you note.) Instead a filter spanning the different projects can be created and saved,…

Hi @Kate Tokar and @Trudy P Claspill I believe it can be done in one rule... For company-managed projects, JQL using the parentEpic() function can be used to find the issues: https://support.atlassian.com/jira-software-cloud/docs/jql-functions/#parentEpic-- For an example query, assuming the parent is the trigger issue:…