The reporter specified is not a user when creating a ticket.

User is taken from AD, the account is unlocked and synchronization is up to date.

When creating a ticket, the field Reporter recognizes the user but returns a "tje reporter specified is not a user".

This happens with some users, the rest works fine.

I couldn´t get a pattern with the users that failed, and also happened that a user that used to fail, started to work "magically". smile

I don´t know what can be happening, can you help me?

Thank you!!

3 answers

0 vote
Steven Behnke Community Champion May 26, 2016

Can you confirm this happens with customers through the portal, or users through the JIRA interface?

We are not using JIRA Portal yet, this happens through JIRA Interface.

 

Hi, is there any bug about these? Or could it be something withh AD sync?

At the time AD sync seems to be perfect, I also forced it and was done successfully (I have 3 domains synchronized, all of them working fine and up to date sync).

Thank you!

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,308 views 14 20
Join discussion

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot