Auto Transition Issue on Creation Based on Reporters Domain

Eric Sara
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 3, 2019

Trying to be clever here and hoping someone can help me achieve what I am looking for. 

Business/Use Case
We use JSD for our external customers to log support.
We want the best of both worlds where most of them can simply log calls as needed. Hence we have customer permissions set that anyone can email the service desk.
And we want to have some customers who can control who within their organisation can email in support.
So I was thinking to put in a rule that if Person 1 or Person 2 are note the reporter then put the request on a status of "Non Authorised Reporter".

How I was trying to do this
The only way I can see that I can tell if a the customer emailing the request is from an organisaion is via their domain.
So using the custom field "Domain of Reporter" I added an Automation that said...

  1. When = Issue Created
  2. If = Domain of reporter = <domain>
  3. Then = Transition to "Non Authorised Reporter"

If this worked I was then going to add further condition to point 2 where the report was not Person 1 or Person 2.
However, using the above it is not transitioning to "Non Authorised Reporter" when a customer with the domain set in point 2 emails in a request. So no point adding the additional conditions at this stage. And just in case you were wondering, yes there is a transition from the First status to "Non Authorised Reporter" set in the Workflow.

Can anyone see why the request is not transitioning?

or

Does anyone have any other ideas on how I can do what I need?

1 answer

1 accepted

1 vote
Answer accepted
Petter Gonçalves
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
June 5, 2019

Hello Eric,

I was able to create an Automation rule that properly transitions the issue depending on the value of the Domain of Reporter custom field, just like you need.

Please, check the steps and verifications I did to make it properly work:

1 - Added the Domain of reporter custom field to the project screens

2 - Configured the following rule:

Screen Shot 2019-06-05 at 19.34.33.png

Things to keep in mind:

1 - Make sure your workflow is properly configured to execute the transition you set in the Automation rule, double-checking if there's any validators or conditions that might be blocking the issue to go through. P.S: Note you are setting a transition in the Automation, not the status.

2 - Make sure the user you configured to be executing the automation rule has the permissions to perform the transition. In fact, try to manually transition any issue to the status with the user, unless you are using the default automation user.

Screen Shot 2019-06-05 at 19.39.46.png

Let me know if this information helps.

Eric Sara
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 5, 2019

You champion.

I had the same set-up as you but the gold nugget you supplied me with was what the transition to the status needed to be able to be done by the user. I was not thinking of this form the point of view of the customer. While as an agent I could move the request to "Non Authorised Reporter", because the customer could not it was not working. Now that I have added that as a transitions that the customer can do the automation works.

Thanks for the help.

Petter Gonçalves
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
June 6, 2019

I'm glad to know my instructions have helped you, Eric.

You have done such an awesome job identifying how you could use JIRA functionalities to achieve your need (I never used the Domain of Reporter like that before).

I'm sure this thread will help many other users in the community.

THANK YOU for the detailed explanation of your use case and have an awesome day! :)

Suggest an answer

Log in or Sign up to answer