Auto Fill the "Review Findings Total" beore moving it to Closed

[mummareddy supriya]

"Review Findings Total" is a field that needs to be filled manually. Can this be filled in automatically when the review is closed?

Only the findings marked "Corrected" or "Postponed" from the Review Findings are to be counted.Either we can do it through automation rules are through post function ? If any one knows please suggest me here.Thanks in advance.

[John Funk]

Hi Mumma,

Basically, you can create an automation that increments that field by 1 each time an issue is transitioned from one step to another based on the issue type (I think). These are all conditions to your rule. 

But your custom field needs to be a number type field if it is not already. And you should default the value to 0. 

[mummareddy supriya]

I Configured the automation rule As shown in the below image ,while after closing the ticket ,i got one error as 

JQL condition

No subsequent actions were performed since JQL condition did not pass due to error running JQL:

"(key IN (-431) AND (issue in linkedIssues(-431) AND status in ("Corrected", "Postponed")))" - The value 'Corrected' does not exist for the field 'status'. But Corrected field was there is status. why i'm facing this error .any help should be appreciated.Thanks in advance 

[John Funk]

Is the linked issue in the same project or a different project? Does the linked issue use the same workflow as the trigger issue? 

Because you JQL is checking the status of the trigger issue, not the linked issue. 

[mummareddy supriya]

linked issue is from  the same project only

[John Funk]

Is this a Team-managed project? Company-managed project? Does the trigger issue use the same workflow as the linked issue? 

[mummareddy supriya]

@John Funk Its a Team managed project ,Yes the trigger issues uses same workflow

[John Funk]

So I am hearing that all of the issues are in the same Team-managed project. And that all of the issue types use the same workflow. Is that correct? 

And again, I think your JQL is wrong - I think you are looking for linked issues that are in a particular status - is that correct? Because that is not what the JQL is doing.