Bill Sheboy Expert

I wonder if this is related to the changes with the epic fields, which continue to roll out this week, and how boards show swim lanes by Epics. One of the field changes sunsets "Epic Link", replacing it with "parent" for company-managed projects. At this point, I recommend creating an Atlassian Support ticket…

That check may be added using a JQL condition and the operator WAS NOT IN: https://support.atlassian.com/jira-software-cloud/docs/jql-operators/#WAS-NOT-IN For example, the JQL condition would be after your trigger, and use this: status WAS NOT IN ("In Testing") This would ensure only issues that had never been in that…

Hi @rhylton Short answer: that is not possible with out-of-the-box features of Jira's JQL. Longer answer: When writing a JQL statement, an ORDER BY expression can be added to sort the resulting issues. However that expression has no impact on any list fields with multiple values for each issue, such as Sprint, Fix Version,…

Iterators inside of iterators are possible, but not for the scenario you show in your question. The support team is incorrect in this case. Again, if you want feedback and suggestions on your scenario, please post an image of your complete rule (in a single image), images of the actions / branches / conditions, and an…

Thanks, Andy and Jack...Yes, and it would be good to get clarity on the disposition of this product change. Yesterday I tried answering a question on this same symptom, with this outcome: for me the "Epic Link" was empty and "parent" was populated, when seen from automation rules and the REST API issue functions. Another…

Thanks, @Ajay Thakur That would seem to indicate a problem on the receiving versus the sending side, as Clark describes.

What did you observe happening: an error or the update did not happen as expected? Please show an image of how you tried to use that function. From what you have shown, I would expect the syntax to be this substituting in your original field name and not the created variable: { "fields" : { "keys" :…

Is that a custom field as it is not a built-in smart value for {{release}}? Please post an image of your complete automation rule, the details of any actions, and the audit log details showing the rule execution. Those will provide context so we are aligned on how / where you are trying to update the Fix Versions field.…

Thanks, Quentin. Based on that information, the value issue.duedate appears to be null. Let's write some values to the audit log to confirm that using the Log action: {{issue.key}} has a due date of {{issue.duedate}}; I suspect the smart value is different for your instance, as my answer was based on Jira Cloud. Are you…

Hi @Mafrik Pranks -- 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…

Hi @bartlomiej.jochym Smart values for fields are name, spacing, and case-sensitive. And...the smart values are often different than the displayed field name on the Jira views. I recommend confirming that you have the correct smart value for your field using this how-to article. Essentially you identify an example issue…

Hi @Rupert Willis Context is important for automation rules. 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…

Hi @Rees, Ian I have not tried either of these approaches... Have you considered using an Automation for Jira rule to initiate the call to the service (with Send Web Request), triggered on Version Created and sending the author information from the {{initiator}} smart value? (Initiator is the user who performed the action…

Hi @Achmad Rifki First thing: are you asking about the view of the board or for the board and backlog? Jira boards (and backlogs) are based on a saved filter, and the default is ORDER BY Rank ASC. When that is used, the drag-and-drop features for moving issues up / down in position work. But if the filter sort order is…

Hi @Mohssine -- Welcome to the Atlassian Community! What problem are you trying to solve by doing this? That is, "why do this"? Knowing that may help to the community to offer other solution approaches, because... Although an automation rule can change an issue type, I would not recommend that. There are several things…

Hi @Sanshia Wadhwa Jira, and its related features and products, are just tools. They can be used for various different process and domain areas. I find Jira's boards for Scrum and Kanban features adequate / okay for use by agile teams...typically for simple, stable process flows. However for projects using a waterfall…

Hi @Anne Varghese There is nothing in out-of-the-box JQL to compare date fields. JQL is not an SQL, and so does not have such features. How often do you need to perform this query? * need this often: investigate either a marketplace addon for JQL or using automation rules * need this infrequently: export the issues to a…

That error is indicating the denominator in the expression (after the divide operator) is null...and so perhaps one of the fields is empty or the smart values are incorrect. Please copy and paste the expression you are using to set the "Live Remaining Time" in a message. That will help us review the cause.

When editing a field, you cannot use both the selection from the drop-down list and the JSON edit. What value(s) are you trying to set in the fix version field?

Hi @Sonja Altmann Yes, that is possible. When you create the issue in your automation rule, some fields offer the option to "Copy from parent". For other fields, you may reference the parent issue's smart values. If that does not help, please post an image of your complete automation rule, including the details of your…

Hi @lila As this thread is quite old, I recommend creating a new question and linking back to this thread. That will ensure more of the community sees it to offer suggestions. Otherwise only the people following this older thread will see it. Thanks! Until we see that question... Did you notice the ... options to the right…

First thing: I have never used that marketplace addon. That seems an unusual response from a marketplace vendor. You may want to let Atlassian Support know about the situation here: https://support.atlassian.com/contact/#/ Regardless, the addon may be using a Jira user's permissions to perform actions to create an issue.…

Hi @Brian Taylor That text is covering part of your audit log image, and it seems to show that the lookup issues action returned no issues, and some other possible causes: Do you have one, or more versions in your trigger issue? If more than one, you may need a different syntax for that JQL. Smart values are name, spacing,…

Hi @Arcy Rhian Fadri -- Welcome to the Atlassian Community! As Freshservice is a marketplace addon to Jira, you may want to check their documentation or contact that vendor's support from the marketplace: https://marketplace.atlassian.com/apps/1218843/freshservice-to-jira-service-management?hosting=cloud&tab=support Kind…

Hi @carlos sarrate Do you already have a rule started? If so, please post images of your complete rule, the actions / conditions / branches details, and of the audit log showing the rule execution. Those will provide context for the community to offer suggestions. If you have not started a rule yet, have you tried doing…

Hi @flaimo It seems those changes are still in-progress of rolling out, as described in this response from an Atlassian employee to a similar question today: https://community.atlassian.com/t5/Jira-Software-questions/When-will-the-quot-Epic-Link-quot-and-quot-Parent-Link-quot/qaq-p/2546760#M303059 And from my…

Hi @Paul Pasler _Seibert_ Please try using the function asJsonStringArray for that syntax: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-json-functions/#asJsonStringArray Kind regards, Bill

I am glad to learn that helped! For your next question, when creating the new issue you may reference the smart values of the trigger issue, as described here: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/ Specifically to do what you asked, try entering this in the Summary during the issue…

Hi @jmweli That is the issue's Key field. Kind regards, Bill

Hi @Shari Brown The issue field changes trigger only detect the changes and not the values. After the trigger, you may add Conditions to check the values before the rule proceeds: https://support.atlassian.com/cloud-automation/docs/jira-automation-conditions/ I also see the audit log is showing an error for invalid JSON in…