We're on 5.1, so I'm using the validators in transitions to make fields required as a ticket moves from step to step. However, Create isn't really a transition. How can I make a field required at the time of the initial save?
No, you don't need the JSU to do this. Jira has, as Joe says, mandatory field options built into it.
Go into the field configuration scheme for the project, find the one you are using for the current issue type and you'll find there's a list of all the fields. There ARE mandatory/optional flags against almost all of the fields (certainly all the custom fields)
There's a lot to be found, I don't think any new admin is able to find it all straight away! (I certainly couldn't when I started with it, and Jira was a lot more simple in version 2)
It's quite likely your documentation is trying to cover the scenario where you don't want a field to be mandatory ALL the time. Jira doesn't really do this - the field configuraiton makes a field mandatory from "create" onwards, so it can never be empty. The use case here is for things like "we don't know what the root cause of an issue is until we've investigated properly, but we don't want to close issues without a root cause". That's when "make field mandatory" validators kick in!
Sorry if I'm missing something, but will this not make the field mandatory for all screens using that field configuration? That is, not just the create screen? What is the simplest way to make the field mandatory only for the create screen? Also, is it possible to associate a field configuration with a screen? Not and issue type or project. If I have only one issue type within 1 project but want a custom field to only be mandatory for 1 screen what are my options?
Please, do not conflate field configurations and screens. They are totally independent artefacts (so, no, you can't associate a field configuration with a screen). It's better to not even talk about them together, as people get confused.
If you want something mandatory on create, but able to be blanked out later, you need to set it optional in the field configuration, and use a validator on transitions where you need it filled in.
If someone in 2016 wants this feature there is the new plugin Workflow Essentials for JIRA. Its not free but will solve this problem very well.
In general: Edit the Workflow and in the Workflow Diagram click on the "Create" Transition and add the Mandatory Field Validator.
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
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