Bill Sheboy Expert

Owen, would you please post images of your rule and the audit log details, and what is not working as you expect? That may help the community give more focus to help. Thanks!

Thanks, Curt!

Hi @Troy Parish I believe you have summed up the issue and a solution/work-around: the timing of the delete trigger firing is leading to the absence of information...preventing the rest of the rule from functioning as designed. One work-around would be not to delete, or not delete immediately. Instead use an "abandoned"…

Hi @Ravi Koorapati What problem are you trying to solve by doing this? Knowing that may help the community to offer suggestions. For example, it seems like you are asking: how to list the issues that have been in multiple sprints when they move to "Need Testing". Why is that relevant/helpful to the team? There are no…

Hi @Owen Schikhof Please try writing the description of an issue with such mentions to the automation audit log in a rule, and you will see how the text and list functions could parse the results. For example, a description may contain something like this when written to the log: here is some text, followed by a link to an…

HI @Andra Vilcea Some yes, and... items for Jack's reply: There are several open requests in this area, starting with there is no public REST API function to get the team/advanced roadmap data, and so there are no automation smart values/functions to use them: * https://codebarrel.atlassian.net/browse/AUT-2138 *…

Hi @Prabhu Chilukuri For Jira automation scheduled rules, the trigger is based upon a time frequency and does not look at the details of the issues for the frequency. Instead you decide the frequency to run the rule, and perhaps add JQL to supply the issues. However, JQL does not have any built-in features for business…

Hi @johannesm I find that advanced branching occasionally needs "help"; sometimes it parses the source as a list and sometimes not. Two approaches for your source list are: * save the match() result in a created variable (which forces to text), and feed that into the advanced branch using split(",")…

Thanks for clarifying, Anton. I suggest trying to diagnose this from one end to the other... * start by calling your request from a browser or other tool to confirm it returns what is expected* if it does not work: investigate your endpoint * if it does, proceed... * next try calling a different endpoint from the same…

Hi @trthomas Regarding the new problem you noted of sending every assignee the list of all issues, you can try to solve that with the list distinct() function, advanced branching, and repeated lookup issues calls: * create a variable with the list of distinct assignees from the lookup issues using…

Ping...to the Atlassian team members following this thread: Should created or branch variables work as parameters to conditional tests (and their included functions) in smart value, list filtering? It seems that they do not. Example use case: Given a list of user account id values driving an advanced branch, use each…

Please check the response from the web request to determine if it was successful. If so, try writing the response to the audit log to learn if the email address was successfully found for the user's account ID.

Awesome! I am glad to learn that helped. The documentation page for managing links does not describe this limitation, so I submitted some feedback for the Atlassian team to take a look: https://support.atlassian.com/jira-cloud-administration/docs/configure-issue-linking/

Did that resolve the problem, or is it still not working for the edit issue case?

Hi Anton, You seem to be trying to call the Jira REST API from an automation rule. If that is correct, please take a look at this how-to article for calling the REST API from a rule: https://community.atlassian.com/t5/Jira-articles/Automation-for-Jira-Send-web-request-using-Jira-REST-API/ba-p/1443828 And, please confirm…

Yes, on the new question posting. One way to get the most visibility of a question/topic is to post a new one and link to any prior ones...especially unsolved ones that have gone "stale". Otherwise only the people following the old threads see what you add.

Awesome! I am glad to learn that helped.

Hi @Calderara Serge First thing, I am using Jira Cloud and not Server/Data Center...so I cannot validate some of what I am suggesting. When an issue is created the Issue Created trigger is the one to use normally. I note the Field Value Changed triggers is documented to also work for create issue for Server/Data Center…

Agreed, and... One opportunity for improvement of Automation for Jira is documentation. For example, smart values should clearly indicate which default attribute is used when they are not fully de-referenced, especially for lists. Sometimes it appears to be {{issue.someField.id}} and other times it is…

I wonder if the link type's name is the problem causing the linkedIssues() function to fail as it contains punctuation. Perhaps try using that query in advanced search to observe what happens: issue IN linkedIssues(TESTFDM-2, "Measures (to fix Finding)") If it works and returns no results, please check your link types with…

Well done! That is what I thought was happening with the missing branch to the created issue. Regarding your second scenario, please see my first comment as that would require a different rule with global/multi-project scope to sync the issue information.

Matthew, thanks for clarifying, and I agree the triggers could allow more flexibility to restrict triggering. For the common use case you noted of updating the Epic Status when an epic is closed, you could do this with a frequently scheduled rule and JQL (e.g. hourly) using Advanced JQL operators and would only trigger…

Hi @Santhosh Sonti -- Welcome to the Atlassian Community! This appears to be an issue with the vendor's plugin gadget rather than the dashboard itself. I recommend going to the vendor's marketplace page, then to their support tab and contacting them for assistance. Kind regards, Bill

Hi @Michael Parker Nested list iterators (and filtering) are possible only when you have lists within lists. Otherwise I find you cannot perform the inner functions on {{.}} as it has not attributes to name the smart values. Instead perhaps consider: * defining what you want to message, * use a single lookup with filters…

Hi @axone That seems interesting... Some of the conditional functions return true/false and some return true/null: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-conditional-logic/ Add to that fixVersions is a list and you do not appear to be accessing a specific list element and I wonder if the…

Hi @trthomas I suspect the issue is in the email body and/or that the lookup issues action returned no results. To fix the second problem, please add an advanced compare condition before you send the email * first value: {{lookupIssues.size|0}} * condition: greater than * second value: 0 If you want to email even when…

Hi @[deleted] -- Welcome to the Atlassian Community! Is the rule image you posted one which received that error? And if so, would you please post an image of the audit log showing the details of the rule execution with that error? Thanks, and kind regards, Bill

Can you please show the details of your rule's edit and link components, and and image of the audit log details showing what happens when the rule runs? I know that "clone" cannot link issues in one automation step, but I thought the Issue Create action could do so. Perhaps this rule also needs multi-project scope.

Sorry, I am out of ideas for this one. The markup differences is one problem and solutions with list iterators cannot easily be nested when there isn't structure to grab. If those template/placeholder sections are stable, the safest approach may be independent custom fields, which you can manipulate easily onto the…

Hi @Kyra Mayock -- Welcome to the Atlassian Community! FYI that for the rule images you posted, one does what you describe and the other (with branch on Current Issue) seems to try to link to back to itself. For your question #2, that would be possible to trigger the rule on the status/comments in the software project…