Bill Sheboy Expert

Thanks, Simon. Like @Angélica Luz I wasn't able to reproduce your results with a Company-Managed project (Classic). Based upon what you describe and your backlog image, it appears to be showing two stories (TEST-11 and TEST-16), both pointing to the same epic (TEST-2) and yet showing two different epic names. How about…

Hi @Beatrice_Dutoit Unfortunately, Lookup Issues does not support the components field yet: https://support.atlassian.com/jira-software-cloud/docs/smart-values-general/#Smartvalues-general-{{lookupIssues}} Here is the suggestion to add more fields to Lookup Issues: https://jira.atlassian.com/browse/JRACLOUD-75018 Best…

Hi @Simon Metz -- Welcome to the Atlassian Community! I note on your screen image of TEST-2, that: * the summary field at the top of the view is "Supply" * the epic name field at the right of the view is "EPIC 2" What happens when you edit the epic name field? Best regards, Bill

Commenting on an issue is a separate action from edit. Perhaps try to add that Comment action inside of the branch, and you may add the value from the trigger issue's comment. Unfortunately this method will not preserve the original author, but you could add that to the comment. Comment from…

I believe trim() removes any whitespace characters at the start or end of the field: https://support.atlassian.com/jira-software-cloud/docs/smart-values-text-fields/#Smartvalues-textfields-trim()

Hi @Paula Manildi I wonder how the newline got on your summary. Doing this should remove it: {{issue.summary.trim()}} Best regards, Bill

Hi @Carolina Meyer -- Welcome to the Atlassian Community! Unfortunately, JQL isn't a SQL, so you cannot access those attributes (e.g. Version Release Date) like you could for an actual SQL for a database. There may be marketplace add-ons for purchase which extend JQL to allow this. If you do not want to purchase an add-on…

Hi @Brian Santos When you navigate to the Releases view, the versions are displayed in release order, with the next release at the bottom of the list. As you note you may drag-and-drop to change the order of release. Changing the sort columns has no impact. (Which is why you should navigate away from that page and back to…

Hi @Laura Guzman That feature idea is in the backlog: https://codebarrel.atlassian.net/browse/AUT-193 Until that is implemented, I believe you would need to rely upon the string functions, including regular expressions, to get your data. Best regards, Bill

Hi @Sayeedul Islam Sumon Agreeing and adding to what @G subramanyam suggests... Consider having a conversation with the team to understand why/when/what the team would change in a description. For example, perhaps the team adds clarifying details or assumptions discovered after work began. If you want to improve visibility…

Hi @Zaldy Parian There is an open production incident for this issue, which you may monitor here: https://jira-core.status.atlassian.com/incidents/zqxvjcl04862 Best regards, Bill

When you edit/update an issue, that issue needs to be the focus in the rule. For example, it needs to be the trigger issue or an issue within a branch's selection. Although you may be able to see the key of a parent with the syntax you are showing, the rule isn't updating the parent: it is not "in scope". Just to be clear,…

Do you mean the Atlassian built plug-ins for Excel and Google Sheets? If so, there are several alternatives which do not require purchasing other marketplace add-ons: * Just export the issues after using a JQL filter search * Use the REST API to pull data out of Jira. There are many different REST API methods so you will…

Your rule is attempting to: * transition all the issues found by the scheduled JQL to Resolved, and then * transition them again to Closed Without Validation. I am unclear why you are doing two transitions. What is the purpose of that? Regardless of that question, the second transition is probably what is un-doing your…

Hi @Matan Grady I believe you need to branch on the destination issue for that smart value to work. Please look at this article for details: https://blog.codebarrel.io/how-to-use-the-linked-issue-trigger-in-automation-for-jira-1616b68c2d6e Best regards, Bill

Hi @Balaji Cherukuri Would you please post an image of your entire rule and the audit log? That will provide some context in case there is another path which is setting resolution. Also, are there any workflow steps happening independently of the automation rule which could impact resolution? Best regards, Bill

Thanks for that information. After your branch starts, and before the Transition, you can edit the Task and choose to copy fields from the Trigger Issue. To do so, after you select a field to edit, select the ... menu at the right, and then Copy From, and Current Issue (which is the triggering issue).

One easy way to find it is with another query. Type in this for a filter search: assignee = Automation When the search shows the user Automation for Jira, select it and the ID will replace the name. That is the value you want to use.

Again, I am guessing here as I do not know what your rule looks like... Here are some scenarios to consider: * Let's say your rule has a scheduled trigger on JQL. That means each issue is processed one by one. As you process each one, use an Action of Log to write the key with {{issue.key}} * You may use the same approach…

Hi @azfar siddiqui If you have the data to set the Task's fields (possible from the Epic) prior to the transition you can set them with the automation. Please post an image of your rule and the audit log from the rule execution if you are still having difficulties. That will help the community provide you ideas to try.…

Thanks for clarifying, and I agree that the audit log seems incomplete in that regard. Without knowing more about your rule structure, I can suggest the following work-arounds: If your rule use JQL to gather the issues, AND did not change the conditions used in the JQL, you could re-run the query later to determine which…

Hi @Balaji Cherukuri Have you tried to use the CHANGED operator in JQL to find this information? First, identify the user id of the Automation for Jira user in your instance. Then try this query: project = myProject AND status CHANGED BY id_for_Automation_User TO "RESOLVED" Please look here for more information on CHANGED:…

Hi @Balaji Cherukuri What do you mean by complete audit log? There are several suggestions for improving what is included in the automation log. If you are having a specific challent with a rule, perhaps posting an image of the rule and describing the symptoms will help the community give you suggestions. Best regards, Bill

I am glad to hear that helped you. Please consider marking this question as answered; that will help others in the community find solutions faster. Thanks!

Thanks for the article, @Esther Strom This is great information! I find using the REST API solves several needs which are currently only long-term ideas in the automation backlog, like this one to add Confluence integration: https://codebarrel.atlassian.net/browse/AUT-269 Best regards, Bill

Hi @Szymon Ptak I meant the source data you have downloaded into the spreadsheet. Please look at how it was exported and use spreadsheet functions to convert to the format you need.

Hi Tim, Thanks for the detailed answers! By the way, I should have sent this link before that has a how-to for confirming which smart values are available, based upon an example story: https://support.atlassian.com/jira-software-cloud/docs/find-the-smart-value-for-a-field/ Okay, let's try to diagnose this from both…

Hi @Denise Wermager In your first JSON example, it seems you have some extra curly brackets; are using update and fields; and are missing quotation marks around the field "name". Perhaps try this, as with a single value you only need fields: { "fields": { "customfield_10108": { "name": "username" } } } Here is a…

Hi @Wendy Ciruli To change the issue type: * Select the issue on your board or backlog * Note the ... menu when the details open at the right of the view, and select Move * From there, you can change the issue type Best regards, Bill

Yup, and there are several suggestions to improve the Classic (now Company-Managed Project) backlog for status. Here are a few:…