The option 'Allow unassigned issues' in General Configuration is currently on. We would like to turn it off, but we cannot do it as the following URL shows.
We should leave unassigned issues which were created before. We would like to refuse unassigned issues from now on.
Do you have any ideas or suggestions to turn it off without changing unassigned issues we already have?
Simple answer - you can't.
You must assign all the unassigned issues before you can turn the option off.
You might think "I can flip the flag in SQL", and it might work, but when I tried it a while ago, it caused huge problems - any attempt to edit or update unassigned issues caused Jira to crash. This was in Jira 4 though, it may be that later versions handle it better, like the mandatory field flag - you'll just get a "you must fill in assignee" on any edit or update. But you really need to test that in a test system before you attempt it in production.
Thank you for your comment. I was just thinking of trying a way via SQL. We can avoid huge problems.
Although we uses Jira 5, we have to test it quite carefully as you mentioned. It's tough work, so we decided to keep the option ON. We will consider a another way to prohibit unassigned issues, such as validators of workflow.
Ok, you could simply change your "field configurations", flagging assignee as mandatory in all of them. You'll still have the problem that you won't be able to edit or progress old issues without assigning them, but forcing people to think about it as they change them might be appropriate anyway! (And this won't crash or anything)
Yup, that's what the docs say to do. I think the questioner wants to skip that.
Of course, if you create an unassigned user, you might as well leave the option enabled - the dummy user subtly distorts your reporting and I find some users find it confusing.
Thank you for your comment. Yes, we would like to skip that.
The first reason is that I don't have the edit permission for all of Jira tickets. We have so many permission schemes and issues security schemes that we cannot change all of them.
The second reason is that notification mail will be sent if I change assignee. That might confuse our customers.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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