Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Changing the reporter field with a smart value and keep getting an error

We currently have a Jira Service management project set up that gets emails from another system and it generates issues. Currently every issue is listing the email address we configured on the other system as the reporter. In the description we have the actual customer's email and I am able to pull it from the description and populate it in a custom email field. The problem I am running into is when I try to make an automation rule that will take the email field and put its value in the reporter field. Currently I am getting the error in the audit logs for the automation rule:

 (Specify a valid value for reporter (reporter))

Here is how I currently have the automation rule setup:

Image 14.jpg

Any ideas or insight into this would be great. Thanks.

2 answers

1 accepted

3 votes
Answer accepted
Simmo Atlassian Team May 19, 2021

Hi @David B,

I think you need to use the Add Customer Action to add the email address as a customer, then try what you're doing.

Let me know how that goes.



Thanks for the response Simeon but that does not resolve the issue, it adds the customer but when I try to assign it to the reporter I am still getting the same error.

Image 15.jpgImage 16.jpg

Simmo Atlassian Team May 20, 2021

Hi @David B

My apologies, I forgot to add the other important step. You cannot reference a user by email address. However, when we add a customer they are accessible via the smart value customer.

You can use this to get the account ID which will be accepted:



I have just tested that and got it to work. Hopefully that should sort you out!




Simeon - 

You are amazing thank you. That seems to be working. Not sure if I need all of the re-fetch data calls but it gets me to where I need to go. I appreciate the help.


Simmo Atlassian Team May 20, 2021

Awesome mate, glad to hear that you got there!

Try it without them, I don't think you'll need them and all it is doing is putting unnecessary load on Jira!

@David B - this is similar to a problem we are trying to solve and looks like Simeon's solution could work for us too! Do you min sharing how you are pulling the customer's information from the "Description" and putting it into a custom field? I assume that is happening in your "Then: Edit issue fields" step with some regex?


@Matt Adorjan -

I use a smart value to pull the string from the description field and set email to it's value:

Screenshot 2021-05-24 101611.png

{{issue.description.substringBetween("email ", " ")}} is what I used, your mileage may vary. is what I found invaluable for a reference to get what I wanted.

Like Bill Sheboy likes this

Hi @David B & @Simmo
I'm dealing with kinda the same issue as mentioned above, trying to "add a new customer" based off a custom field, and then set this customer as a reporter. 
I didn't fully understand what should be configured within the last condition "edit issue filed reporter". @David B could you please share the workflow that worked for you? I see that @Simmo suggested the action {{customer.accountId}}, but it doesn't seem to work for me. 


Simmo Atlassian Team Jul 11, 2021

Hi @Omer Joffe ,

Could you share a screenshot of your rule setup and where you're stuck?

thanks for the quick reply @Simmo !

sure, please find it below.
quick overview - 

  • the issues are being created in JIra by Splunk 
  • fields description -
    • {{issue.fields.customfield_10084}} = account email address
    • {{issue.fields.customfield_10083}} = account name

The first condition adds a new member (if doesn't exist) - 


The second condition is supposed to assign the customer from the first condition as a reporter instead of Splunk.



Audit log - "specify a valid value for reporter".



what am I missing? my goal is to assign the reporter based on either account name/email address.

thanks a lot.

Omer Joffe

Simmo Atlassian Team Jul 12, 2021

Hi @Omer Joffe

In this case, the error is happening with the add customer action. A customer already exists with that email address, so we don't create one so the smart value doesn't work. Looks like you're testing this so try it with made up emails.



Hey @Simmo
yeah, I know this customer already exists, but that's not the case, I've tried this rule many times with different emails and names, but still failing to assign a new reporter.
here is another test from this morning- a new customer was successfully created, but the reporter value doesn't seem to work (I'm using - {{customer.accountId}} as the new reporter value).


Simmo Atlassian Team Jul 13, 2021

Hey @Omer Joffe

Can you raise a support ticket for this? You're doing the exact same thing that I am able to do successfully so I am not sure what is going on here. We'll need to dig into the problem to find out.



Hi @Simmo ,

I created a ticket last week and it was already fixed by a Jira service management engineer. Thanks for your quick reply.

What was the Issue? 
I have the same Error when i try to put in a email from an Interal user but it works for external Emails.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Atlassian Automation

Jira Automation: Sum Up Story Points Roundup (Initiatives -> Epics -> Story/Tasks -> Subtasks)

Hi Everyone, In this roundup we combine all the jira automation rules to sum up story points across different issue types. We start from the lowest level, summing up story points from sub-tasks t...

1,846 views 2 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you