Workflow validator for Reporter !=

[Joe Doherty]

Our JSM integration with Slack often creates support tickets with a default "Jira-Slack" user.

I want to create a workflow validator that makes sure that a support agent has changed the Reporter to the real user, not our default service account.

How can I create some kind of validator with this logic?

Reporter != "Jira-Slack User"

Besides built-in Jira post-functions we have the following Jira Cloud apps:

• JSU
• JMWE
• Scriptrunner 

[John Funk · Accepted solution]

Hi Joe,

I would try the Build-your-own (scripted) Validator (JMWE app). In the Jira expression section select issue fields and search for Reporter. Select the value for issue.reporter.accountID then add != after it. 

Then select Lookup user and search for the generic Slack user. Select insert accountID. So it should look something like:

issue.reporter.accountID != 64542e54534a8e8a3347fd3

Then test the expression. 

Finally add an Error message. 

[David Fischer]

It would be 

issue.reporter.accountId != "64542e54534a8e8a3347fd3"

(lowercase "d" and quotes around the account ID) 

[John Funk]

Ah, thanks, David! Cleaning up my syntax mess as usual haha. 

[Joe Doherty]

Thanks John and David this should be exactly what I'm looking for! 

[John Funk]

Great!

[Samuel Gatica _ServiceRocket_]

Hi @Joe Doherty 

In the transition to In Progres, you can add the Value Field condition and set the parameters, the transition to the next status will not show if the Reporter is set to the "Jira-Slack User", here is an example

Hope this helps

Best regards

Sam

[Joe Doherty]

Thanks @Samuel Gatica _ServiceRocket_ - if I use a condition then the transition will just disappear (and I'll get reports "why is Close Issue button gone?").

I'd prefer to use a validator, so when the user clicks "Close" from the transition screen, it will throw an error and the user will have an opportunity to update the Reporter to try again.