Bill Sheboy Expert

Hi @Creative Ideas -- Welcome to the Atlassian Community! Adding to Alexis's answer... Your description appears to contain newlines (line feeds) and so building on the earlier suggestion, the result could be split() and then grab the first result. For example:…

Hi @Mats Rahm I see one problem with your rule and several possible improvements... The problem is your condition with JQL on sprint IN ("NPS Mavericks"). This type of JQL will perform an exact match on the sprint name, but your sprint names apparently have other characters in the names, such as the program increment…

Hi @Piskorz Magdalena (BD/BTM-IC1) 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…

Hi @Olive Sun Adding to John's answer... What markup / formatting features are you using in your description field? Does it all not convert or does only some of it not convert? There is an open defect about table formatting not working correctly: https://jira.atlassian.com/browse/AUTO-409 If that is the case, some…

Hi @Gal Fatal The Issue Created trigger can fire so quickly that some of the issue data may not be available to the rule when it starts. The symptom of this is other rule components do not work as expected...for example: perhaps the parent field is empty. The work-around to check if this is causing the symptom is to always…

Thanks for the update, Trudy. Did you let them know the REST API function the documentation suggests (for finding supported smart values) seems out of sync with that information?

I wonder if the call is encountering this defect, where using the content-type key is causing a duplicated header: https://jira.atlassian.com/browse/AUTO-98 Do you have logging on the receiving side to check the sent calls?

Hi @Leena Pratheepan When you branch to the parent issue (i.e., Epic) it cannot see its child issues' data. Instead try using the Lookup Issues action with JQL to gather the child issues, and then use the sum function: https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Lookup-issues For example...…

Hi @paulius.janulevicius Adding to Jack's suggestions... Are the values in the condition reversed; don't you want to check if the initiator's account ID value is not present in the list of possible values? As shown, that condition would test if the initiator does not contain the entire list. Kind regards, Bill

In your branch JQL, it has this: issue IN linkedIssues({{issuekey}}) I believe it should instead be this: issue IN linkedIssues( {{issue.key}} )

Hi @Sebastian Müller -- Welcome to the Atlassian Community! First thing: what problem are you trying to solve by doing this? The issues with the same Fix Version value can already be found using that field, so the linking seems redundant. Next, the Lookup Issues action is not dynamic like you show. You must first use the…

Is there anything dynamic about your request URL, such as including smart values? If so, have you validated it by writing the expression to the audit log prior to the Send Web Request action?

I am using Jira Cloud, not Server version, and have not tried that with Insight fields. Have you tried using the advanced edit with JSON to copy the data from the trigger issue, rather than using the drop-down list of fields?

Thanks for that audit log image, as it shows the smart value added to the JQL for the linkedIssues() function is null / empty. Would you please show images of your entire rule and an image of the branch details with the smart value in that function? That context may help explain what is happening.

Sorry, I am out of ideas on this one. You may need to wait for someone using Jira Server to comment further, or work with your Jira Site Admin to ping the Atlassian Support team to learn what they suggest.

Did you try writing that request to the audit log to review it, ensuring it matches what you expected?

Hi @attaf sheikh If this is a temporary symptom, and so necessitating some temporary measurement to help, you could do the following: Export the issues from recent sprints to a spreadsheet, count the sprint values per issue with spreadsheet functions, visualize that data, and use it to have a conversation with the team…

Hi @Alex Cadevall -- Welcome to the Atlassian Community! Just to confirm: for the issue triggering this rule, how many versions are assigned to Fix Versions? As written, the rule would only support one value in the Fix Versions field. Having multiple values would cause an invalid URL for that request. Kind regards, Bill

Hi @Juergen Holzer Please try to stick to one conversation thread when posting. That will help others looking at this question in the future see if there were multiple possible solutions. Thanks! Next, please post images of your entire rule and the audit log details for context. Finally, please confirm the following: * Are…

Hi @Marcel Rossouw As this is an older thread, you may want to create a new question and link back to this one for context. That will ensure the maximum number of people see it to offer ideas. In the meantime... Without seeing your complete rule and audit log details, and the details of the action with the symptom, it is…

I've seen that when my URL for the service is incorrect, or there is an outage on the receiving side. I recommend diagnosing that symptom separately, such as calling the service with a mechanism outside of the automation rule. That will help fault isolate it, and once it is working again, return to testing with the rule.

Thanks for the confirmation of your Jira version. To sum a numeric field for a Lookup Issues result set, please use this syntax: {{lookupIssues.customfield_123456.sum|0}} I added a default value of 0 to the end to handle the case of all values are empty / null.

Hi @German Dobrilovich What is the scope of your rule: project, global, or multiple-projects? And if it is project scope, in which project is your rule stored? I hypothesize your rule is project-scope and not in the PRIUR project. Thus the rule only has visibility to issues in the rule's project, and so the JQL returns no…

Hi @Szymon F To set the Fix Version values with JSON the attribute is "name" and not "value". Please look here for more information: https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/#Fix-Versions If that does not work, please post images of your Create Issue action and of the audit log…

Hi @krunoslav_majer First thing: I am not using JSM and so cannot test what I suggest. Have you tried to use the generic Issue Updated trigger to see if that will start the rule? Then you could use this how-to article to determine if the field / information about forms is available to automation rules, accessible as a…

Hi @Howell Looping would not work because a smart value, list iterator can only "see" the data from the scope of the iterator, and lower. For example, when iterating over a Lookup Issues result, only data in the lookup can be seen. (i.e., not any looping variable like your Team and Priority values) A work-around to do this…

Hi @Christopher Kim 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.…

Thanks for the screen images. In your rule's Create Issue action, you have selected the Original Estimate field from the drop-down list and tried to set the field with advanced edit with JSON. If you review the audit log details when trying to run the rule you should see an error. Only one of those edit types can be done…

Hi @Trudy P Claspill First my disclaimers: I have not tried to use hierarchyLevel in rules before, and I'm trying this with the Free license version of Jira. Using the REST API to check for supported smart values for rules, both avatarId and heirarchyLevel appear to be supported as you show for various issue…

Hi @Vincent -- 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 provide context…