"Assigned To: Assigned To is required." error

Over the weekend, we were no longer able to create JIRA issues and were receiving errors such as "Assigned To: Assigned To is required." or "Due Date: Due Date is required."
Was a change made to JIRA fields for "Assignee" to be changed to "Assigned To:"?  We use several workflows and I don't want to have to manually edit them all for my team to be able to create tickets again.

If anyone else has this issue or know how to resolve it I would appreciate it. Thank you!

Here is a screengrab of the error:

1 answer

1 accepted

1 vote

One of your administrators has made the "assigned to" and "due date" fields mandatory in that project, either with field configurations or with validators in your workflow.

You'll need to undo that change, or probably limit it to the project(s) where they intended to do it.

This is exactly what the issue was. A less-experienced team member changed a global setting in JIRA while trying to customize a project workflow.
Thank you for the reply! This issue can be closed.

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,223 views 14 19
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