Vishal Biyani Expert

Thanks for the details. This is great progress you have made. The issue is at least isolated. Let me think through more what else could be the issue and will respond back tomorrow morning 

Good to know that this worked for you

print remaining days enclosed in pipes {{ #debug }} |{{ remainingdays }}| {{/}} if there is any extra character like space, we will know by seeing a gap between the digit and |.

@Ramamani Ramaraj (T CST CSI-US) Can you elaborate on the problem statement? When you Card are you talking about the jira board or the issue fields? What fields do you need to add?

if you have confirmed that permission for the filter looks like Then to debug, can you run the filter in jql and check how many issues are returned?

@Armando Calvache i suspect you have issue due to filter permission. Can you check what is the view permission and confirm?

This may require project Admin privileges. Check with you Admin

@Duc Thang TRAN with toDate you need to specify the format. Are you doing that? Once string is converted to date, use .format to update the date format .toDate("yyyy-MM-dd").format("MM/dd/yyyy H:m:s ")

@Shamima Essop How is your board configured? Can you check the query that is being used to rule out that the query filters out Epic configure board -> General.

please share the SS of your audit log to understand what error message you are getting

@Armando Calvache Have you given view permission to the filter? if it is private then automation will give error

@Armando Calvache To better format the email given that there could be multiple issues, you can format your email with html table like this <table border="1" style="border-collapse: collapse; width: 100%;> <thead> <tr> <th style="text-align: left; vertical-align: top;">Issue Key</th> <th style="text-align: left;…

This may not be feasible using JQL. issueFunction is provided by ScriptRunner. Possibly you have Script runner in Server

@Tehmina Aslam Can you copy the calculation in smart variable and then use that smart variable to update the issue? i think it should help resolve the issue. Also there looks to be an extra [ bracket before Issue. That is not needed Share your audit log as well

@Niklas Zarnecke Before branching into parent, can you try copying the trigger Issue values in smart variable. Then use those values to compare with parent status. See if this helps resolve your issue.

tipi.chaibamrung@posti.com can you run below query project = Your Project and Sprint = <sprint that you want to investigate> and (statusCategory != Done or resolution IS EMPTY) See if this returns any issues

@Sanam Malleswari Nice explanation!!! In terms of 4th point, I see Team field (provided by JIRA) is a "single select" Field in my cloud instance. Is there any setting that you know of using which multiple Teams can be assigned to an Issue?

tipi.chaibamrung@posti.com Are all the 84 tickets that are you are referring to a sprint in Done statusCategory? if not, that will explain why some of the open tickets are moved to next sprint or backlog

add a log statement specifically for issue.customfield_19832 Need to see what else needs to be added to this variable to ensure it is picking right value

From Epic, if you Click on + button (Child Issue), I see the standard issuetypes like Story, Task etc are available.

if you see the log message, RootCause is not getting value. Add debug statement for issue.customfield_19832 to see what value it is having

@Mohamed Eid Looks like the Regex expression for remaining days is not working. Can you check if this is having any extra spaces or something like that? if remaining days gets populated i think the rule will work. To test the theory, you can try hardcoding the value of remaining days and see that you are getting the final…

I don't have much experience using confluence APIs and Postman. Better to post the question tagging confluence, so that folks who are experienced in Confluence APIs can respond. In terms of permissions, given that confluence space has permissions, so you would need to have permissions to query the space.

The response is a json object. You will need to parse it. This is enclosed inside results list

@Gomathi Sundarraj Can you share how your CSV file looks like? How are you mapping the fields while doing the import?

Great. If this works for you, please accept the answer

like this https://<domain-name>/rest/api/3/issue/OS-663?fields=summary

Can you share the SS of the last step i.e edit issue Field? Also, share the history of what Updates happened after the automation was run

Try with {{#issue.fixVersions}} {{ name }} {{/}}

@İclal Aslan JIRA Automation does not allow deleting of work logs. However, a combination of JIRA Automation and REST API calls * to get the worklog * delete the worklog ID received in above request will be required You can refer to this article