Thank you for the reply.
I have added a validator ( Required Fields ) on the Create Transition of the Workflow with the help of JMWE Addon.
Hi @Roja Gurram ,
You are able to enforce the Security Level field being required via Field Configurations.
The Assignee field does not have this ability out of the box, so you would need to look at a plugin that lets you place a Field Required validator on the Create transition of the workflow such as JMWE or JSU.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
In the global settings, you can also disallow unassigned issues, but that is a global setting.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Nic,
Am unable to find the global setting. Is this something like GLOBAL PERMISSIONS ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sorry, that was vague, I usually remember to include the route.
Log in as an admin and then go to
<admin cog> -> System -> General configuration -> edit settings
Look for "allow unassigned issues" in there and set it appropriately. There are some things to think about when you are going to change this, but Jira will explain them better than I can.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.