I need to validate the Field "Due Date" on 4 issue types.
The first 2 issue types is working like dream, but the last 2 is not validating at all.
On closer inspection I saw there is in actual fact 2 "Due Date" fields to choose from. When I search for it in the Custom field section I only see 1 "Due date" and not 2.
I deleted "Due Date" on the issue types that does not want to validate the field and used the other "Due Date" field. When I open those issue types, the Due Date field is not visible anymore.
This has been grinding my brain for a week now.
Any ideas how to rectify this? We upgrade to JIRA 6.3.5 a week ago from JIRA 5.2.3
"Due date" is one of the system fields, so it will always appear. Creating a second one as a custom field is confusing and noisy, and I suspect you've realised this. I'd delete the custom one completely if you can (or at least rename it to "deprecated due date" so people avoid it)
To make the system due date appear, you need to check over two things - the "field configuration" could be hiding it from the project/issue type, and/or it may not be on the "screens" you are using. Take a look at the config for the first two issue types, because those are working, and compare the screens and field configurations with the issue types that are not.
(And if you are going to bin the custom due date, I'd recommend removing it from create and edit screens, so no one can use it)
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
Hi, everyone! Molly here from the Jira Service Desk Product Marketing Team :). In the spirit of this month's august-challenge, we're sourcing stories of Jira Service Desk activation fro...
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!
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