Bill Sheboy Expert

Are you using a condition on the trigger (i.e., the new feature just added) or using a separate Smart Values Condition after the trigger?

That is curious...time to test and verify! When I just edited the Description in a JPD Idea, with a rule using Work Item Updated, the changelog did not contain the Rank field in all four ways I checked it: * write {{changelog}} directly to the log * capture the {{changelog}} as a variable to see its raw content, writing…

Hi @Peter McCann To use the {{lookupIssues}} smart value, you need to first add the Lookup Work Items action to the rule. For your scenario, inside the branch as a first step, add this: * ... * branch: to parent* action: lookup work items, with JQL of* parent = {{issue.key}} * action: edit work item fields, to update the…

Hi @Keiko Kamiya Correct: the date and date / time types are not supported for a Manual Trigger's user input options yet. That is one of the suggested improvements to the trigger, which you may watch / vote for here: https://jira.atlassian.com/browse/AUTO-744 As a workaround, please use a Short Text field, and later…

Hi @Cameron MacKenzie -- Welcome to the Atlassian Community! Some smart values are loaded dynamically, and this can create latency / timing problems with things like the Send Web Request action in the dynamic JSON, the URL, etc. The same symptom can happen with Create Work Item and other actions use of JSON. Please try the…

Hi @Michael Ball-Marian -- Welcome to the Atlassian Community! First, what problem are you trying to solve? That is, "why do this?" Knowing that may help the community to offer additional suggestions. Next, what version of Jira are you using: Cloud, Server, or Data Center? I ask that question because with Jira Cloud, the…

The JQL in the Lookup Work Items action is still incorrect. It should be this: parent = {{issue.key}} I recommend carefully reading what the community suggests. This will save you time and reduce errors when trying to solve rule questions / problems.

Thank you for clarifying the format, and... Please note this may a brittle solution as a person could easily "break" the template when entering the Description field. Providing them specific custom fields to enter may be better. Regardless of that challenge, please try using text functions: You could use either…

Hi @Charles Brooks After you have defined all possible cases for testing, as Trudy suggests, you could use a math expression and the MAX() function to ensure the value is always at least 1. For example: {{#=}}MAX(1, {{issue.customfield_11957.diff(issue.duedate).days}} ){{/}} Kind regards, Bill

That should not be the case with if / else block conditions. Please post an image of your complete rule, in one single image for continuity. That may explain why the rule does not work as expected. Thank you!

Hi @Carlos Barros -- Welcome to the Atlassian Community! Adding to the suggestions from @John Funk and @Mikael Sandberg ... There is no else conditional expression as you tried. Here are the supported formats to do that: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-conditional-logic/#if For what…

Hi @Hector Vega -- Welcome to the Atlassian Community! Both of the expressions you note return string values for the date: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-date-and-time/#Date-format--- The symptom may be related to related to how the date is parsed just-in-time when stored by the rule…

@John Funk -- I believe the log now shows the Parent matching and the Subtasks not matching the JQL. Perhaps one of the earlier post's edits showed it the other way? @Mahnoor Arshad -- without seeing image for the condition I asked about... First, you seem to be using Jira Server or Data Center. Is that correct? Next, it…

Hi @Mahnoor Arshad -- Welcome to the Atlassian Community! Please explain what you mean by "is no longer executing properly". Specifically, what do you observe happening and when / what steps proceeded that behavior? And for more context on what you are observing, please post images of: * your condition in the branch which…

Hi @Stephen Johnston -- Welcome to the Atlassian Community! Yes, that is possible using a trigger on a change to the Sprint field, a check on the changelog smart values to confirm the work item was in the active sprint, and then add the comment. Please note a rule like this can be challenging as there are known problems…

Hi @Carolina Catalani -- Welcome to the Atlassian Community! There is an automation rule action to do that, although I have not used this one: https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Create-Slack-channel-for-incident Kind regards, Bill

Awesome; I am glad to learn it is working! Please consider marking this question as "answered" to help others with a similar need find solutions faster. Thanks!

When posting rule images, please post the entire rule in one continuous image and post the relevant actions as separate images. That will provide overall context for what is happening. Until we see that... When creating a rule like this, I recommend writing intermediate results / smart values to the audit log with the Log…

Where did you use that JQL in the rule? The error indicates there is no value for {{issue.key}} at that point in the rule. For the rule you currently show (as the time of this post on 10 July), the JQL would be with the Lookup Work Items action inside of the branch to parent. And so that error is not possible when there is…

Hi @Baudoin Guiot Desvarenne -- Welcome to the Atlassian Community! I am seeing the same symptom, and so I wonder if the recent updates to audit logs have bent / broken something. The only open, related audit log defects I see in the public backlog for this are for the recent changes to add Advanced Component features. As…

Hi @dominiclau.intern -- Welcome to the Atlassian Community! First thing: what problem are you trying to solve by doing this? That is, "why do this?" Knowing that will help the community offer better suggestions. Next, your question describes parsing / checking text in the Description field for missing content, but the…

Hi @Fiona Lauchlan Yes, that is possible when the values of the source fields match your destination fields. Have you tried to create the rule yet? * If you have and the rule is not working as expected, please post images of the rule, audit log details, and explain what is not working as expected. Those will provide…

Hi @Luka Recine 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, there is still only limited documentation for these new features, with this recently added for group configuration in…

Hi @Mitesh Mistry -- Welcome to the Atlassian Community! 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 @Vinnasoft 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 @Chance Douglass 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, and kind regards, Bill

Hi @Samrat Mazumder 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 @Korbin Perry 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 @Louise Baker 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 @Normand Raby -- Welcome to the Atlassian Community! 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, have you tried using a Lookup Table for the mapping of keywords to category…