Automation condition - if comment is from approver

[Stanislav Borisov]

Hello,

I am trying to trigger a status change when a comment is added from approver. This is what I have so far but no success. Tried with other smart values as well:

[Jovin · Accepted solution]

Hey @Stanislav Borisov 

Until the approver has approved the issue it won't appear in there. Instead, you should look to see if the user who commented is in the Approvers field (or a group if there is a specific group).

For the field you could use the below in your condition:

1st Value: {{issue.Approvers}}

Condition: Contains

2nd Value: {{initiator}}

Hope that helps!

[Stanislav Borisov]

Hello @Jovin
Much appreciated, works like a charm.
Regards.

[Stanislav Borisov]

On a second thought, this is working if the approver is a single user. What about a scenario when all users in approvers filed must comment and only then to do the transition?

Regards,

[Jovin]

Hey @Stanislav Borisov 

Let's dive into the process a bit - is there a reason you're looking for a comment from all the Approvers, instead of just clicking the Approve button, and requiring all people in the field to approve?

[Stanislav Borisov]

Hi @Jovin 
Lets just say due to intra-organizational reasons and we are looking for a solution outside of the box.

[Jovin]

@Stanislav Borisov 

No worries then, off the top of my head I would do the following (may not be the best solution, but it'll work):

1. Create a new custom field "Commented Approvers", this will be a User Multi-Pick field type. It's purpose is to track the approvers that have commented on the issue.
2. Ensure this new field is NOT visible on any screens, unless you want to see it, even then I'd recommend splitting your View/Edit screen configuration to be a separate View screen with the field, and Edit without (this makes it read only).
   1. For more on this see: Manage Issue Screens 

Once this is done, we're going to update your automation rule as below. This updated rule will keep track of the approvers that have commented, and then check if the "Commented Approvers" contains ALL of the Approvers, if it doesn't it won't transition.

• Trigger: Issue Commented
• Condition: Issue fields
  • Field: Status
  • Condition: Is one of
  • Value: Waiting approval, Waiting for approval
• Condition: Smart value
  • 1st Value: {{issue.Approvers}}
  • Condition: Contains
  • 2nd Value: {{initiator}}
• Action: Edit Issue
  • Field: Commented Approvers (our new field)
  • Value: {{issue.Commented Approvers}}{{initiator}}
    • By doing these values we append to the list instead of replacing
• Condition: Issue fields
  • Field: Commented Approvers
  • Conditions: Contains all of
  • Field: Approvers (from current issue)
• Action: Transition issue
  • Destination status: Waiting for support

[Stanislav Borisov]

Hi, thank you for your reply. I did the steps as you can see below on the picture, but I get two scenarios and none of them work properly:
1. I add two user in approvers field. When the two users reply from email, the custom field Commented Approvers updates and both of them are captured, but the transition does not happen.
2. I add two users in approvers field. When one of them adds a comment from the portal, the transition is happening (something that is should not happen).
Please advise.

[Bill Sheboy]

Hi @Stanislav Borisov -- Welcome to the Atlassian Community!

After the Edit Issue action, please add a Re-fetch Issue action to reload the data before the condition tests the approvers.

By default, rules updating issue fields update the database in the cloud, but not the in-memory copy of the issue the rule has.  This is both for performance and when the original data is needed by a rule.  The Re-fetch Issue action will reload the data from the cloud before proceeding.

Kind regards,
Bill

[Stanislav Borisov]

Hello @Bill Sheboy 

Thank you! This did the trick. Much appreciated.

Regards