Bill Sheboy Expert

Hi @[deleted] -- 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…

Hi @Moreno Gonçalves I would expect that to be shown. When you look at the Sprint Report, what do you see for scope change? Kind regards, Bill

Please see my first post in this thread, as it shows the {{content}} attribute of attachments, which provides a URL a licensed Jira user can access.

Hi @Bert Dombrecht An FYI regarding your note: 'Parent' typically refers to a Sub-task Parent in Jira. With the change to sunset many of the Epic fields and use the parent field for most parent/child relationships, a branch on parent, rather than Epic (parent) could refer to either: * an Epic (from a Story / Task / Bug) or…

Hi @Tomislav Tobijas Probably, depending upon your Jira version (and thus your version of automation rule actions). If you have Jira Cloud, you may use an Advanced Branch to iterate over the values of a field / smart value list, as described…

When you use the function asJsonObjectArray() it returns most of the syntax needed, and so you do not need the brackets wrapping it. And, you appear to have added an # for iteration but that is also handled by the function. Please try this instead: { "fields": { "customfield_10107":…

Looking at that latest screen image, I wonder if the smart value expression you are using is invalid. Smart values are name, spacing, and case-sensitive. Please try using exactly this one, with no changes. I added a default value of 0 in the event the field is empty. {{lookupIssues.Story point estimate.sum|0}} And can you…

I suggest using the Lookup Issues action to gather the results from "query 2"; that will make it easier to then build the dynamic JQL to add to your "query 1" using text functions.

Thank you for clarifying the question. You may do that in the Additional Fields area, using advanced edit with JSON, as described here: https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/#Cascading-select-custom-field The value in that Additional Fields box would be something like this: {…

Are you using Jira Server or Jira Data Center? I can see a Lookup Issues action in your rule, however I thought that was only available for Jira Cloud and Jira Data Center. Does the Lookup Issue action return the issues you expected? If it does, please try this smart value:…

Just a follow-up... Based on your other responses that you want to do a "push" message, I believe you could using an automation rule: * gather ideas with a non-empty date field using a lookup issues action and JQL * parse the field to get the date value and perform a comparison with smart value, list filtering to your…

Hi, Danno! The link I provided for finding the smart values is specifically for Jira Server...the technique the same, with just some differences in the specifics, so please give it a try if needed. Are you trying to update the trigger issue with data from a linked issue? If so, please take a look at the lists in the issue…

You have defined your own method of connecting the issues, with linking or other fields. And so I would not know what to suggest for JQL. Please identify some example issues you believe are related, and then use this information to create some example JQL for find the related…

Hi @Ken Adding to Mikael's answer... I think the smart value to check for the project category is: {{project.projectCategory.name}} or the id value if you want to use the numeric value. Kind regards, Bill

Hi @Danno Until we see your rule details...you can use this how-to article which explains how to find the smart values for an issue. It also shows the structure, helping to know how to get at the information for things like linked issues.…

Hi @Cristin Williams -- Welcome to the Atlassian Community! Just to confirm, are you trying to...Compare something in the trigger issue to a list of allowable values, which is already used in a selection field? If so, you have a couple of options: * hard-code the values in the rule to compare (with conditions, a lookup…

Hi @Vishal Sitpura -- Welcome to the Atlassian Community! I suspect the answer is, "no". The Story create would need the issue key from the created Epic, and the Epic has not been created at the time you submit the JSON. And without knowing the internals of how Jira is processing the JSON we may not be able to assume this…

Hi @Douglas Oliveira Costa -- Welcome to the Atlassian Community! I am curious: what problem are you trying to solve by moving completed issues to a new epic? Thanks! Kind regards, Bill

Hi @Johannes Mayr -- Welcome to the Atlassian Community! You could use an Advanced Branch, over the selected values of your checkbox field, and add a subtask for each one. Please look here to learn about using Advanced…

You appear to already be doing that in your Edit Issue action. That JSON could be copied and used in the Clone Issue action instead. When cloning, any field values can be replaced (rather than copied) if provided in the action. Here is the advanced edit with JSON reference, just in case you want to check your…

Hi @shravani.roy -- Welcome to the Atlassian Community! That is not possible at this time, based upon this other community post, and suggestion from an Atlassian team members: https://community.atlassian.com/t5/Jira-questions/How-to-unlink-a-bitbucket-branch-from-the-JIRA-task/qaq-p/712305…

Hi @Mathias Minsel First thing, here is a how-to article for calling a REST API function from an automation rule: https://community.atlassian.com/t5/Jira-articles/Automation-for-Jira-Send-web-request-using-Jira-REST-API/ba-p/1443828 I recommend creating a basic rule which returns your saved query to confirm everything is…

Thanks for that information, and... The advanced branch can work from any smart values provided, not just from issues. If you provided the components in a created variable (or smart value expression) that could still drive the branch. You note a "sub component". What do you mean by that? Is it a subset of all possible…

I believe you can do that at the same time as the clone action, using an advanced edit with JSON. Have you tried that?

Hi @Simone Longoni You are correct, and... After some digging and experimenting I found that the JPD team appears to have created a new "date range format", which is neither a date field nor JSON compatible. Which is probably one reason it does not work with JQL or directly with automation rules. (Although that second one…

What edit are you trying to make to the newly created Subtask? Knowing that may help to figure out a way to do that at the same time as it is created...eliminating the need for the separate edit.

Hi @rob.morrey -- Welcome to the Atlassian Community! No, the board and backlog cannot be determined directly for an issue, however... * A board (and its backlog) are views of issues in a project based on a saved filter * You have several boards in a project, and so I am assuming that is a Company-managed project, each…

Hi @Emilia KASPRZYK Would you please clarify what you are asking? For example... Are you trying to dynamically change the possible values for a cascading field (for later use in issue create / edit) based on issue assignment? Or, are you trying to set the values of the cascading field, based on the issue assignment?…

Hi @Jaime Basco That is not directly possible with an automation rule for Jira Cloud. A rule can create issues directly, and can call REST API functions, and so a possible work-around (which I have not tried) is to: * attach a CSV file to an issue * have a rule call the REST API function to get the attachment's content *…

Thanks, Trudy! I fixed my earlier post :^)