Error Jira Does Not Allow For Unassigned Issues
Contents |
are turned off10-1meena radhakrishnanApr
Jira Unassigned Filter
15, 2012The server returned the following errors: jira the default assignee does not have assignable permission Assignee: The default assignee does NOT have ASSIGNABLE permission OR
Jira Assignable User
Unassigned issues are turned off. I am getting the above error message when tried to submit an issue default assignee jira from Firefox Bonfire plugin. The default assignee for this project (who is also the project lead) has the assignable permission set. I not sure where to check for the second part 'Unassigned issues'. jirafirefoxaddonjira-captureCommentCommentAdd your comment...2 answers210Jobin Kuruvilla [Go2Group]Apr 15, 2012Allow 'Unassigned Issue' is a configuration under 'General Configuration'. See http://confluence.atlassian.com/display/JIRA/Configuring+JIRA+Options Seems like the default user (project lead) doesn't have 'assignable permission' - maybe set incorrectly and hence it tries to fallback to 'UnAssigned'!CommentCommentAdd your comment...10-1Nathan GivenMar 03, 2015Check your components configuration for your project... if you have components set to be assigned to "Unassigned", then that will override the default assignee setting on the roles screen.CommentCommentAdd your comment...Sign up or log in to answerWatchRelated questions Powered by Atlassian Confluence 5.7.3, Team Collaboration Software Printed by Atlassian Confluence 5.7.3, Team Collaboration Software. Report a bug Atlassian News Atlassian
'Allow unassigned issues'?10-1Shun HirayanagiJul 31, 2013The 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.https://jira.atlassian.com/browse/JRA-22527We 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? jirajira-administrationCommentCommentAdd your comment...2 answers210Nic Brough [Adaptavist]Jul 31, 2013Simple answer - you can't. You must assign all the unassigned issues before you can turn the option off. You https://answers.atlassian.com/questions/48066/unassigned-issues-are-turned-off 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 https://answers.atlassian.com/questions/196466/how-to-turn-off-allow-unassigned-issues 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.CommentShun HirayanagiJul 31, 2013Thank 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.Nic Brough [Adaptavist]Jul 31, 2013Ok, 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)CommentAdd your comment...210Peter Van de VoordeJul 31, 2013You could just create an internal user called "unassigned" and assign all the old tickets to this user. Then it's still clear which are the older "unassigned" issues. Best regards, PeterCommentNic Brough [Adaptavist]Jul 31, 2013Yup, that's what the docs say to
does NOT have ASSIGNABLE permission" error10-1Esther StromSep 24, 2013I've looked around, and found answers that told me that this https://answers.atlassian.com/questions/215496/the-default-assignee-does-not-have-assignable-permission-error is most likely because my default assignee does not have the assignable permission (gee, thanks.) The problem is, the default assignee for my project DOES have the assignable permission. It's set via a project role, which the default assignee (also the project lead) is a member of. We do NOT want does not to allow issues to be created unassigned. Where else can I look for what might be causing this issue?jirajira-administrationCommentEsther StromSep 24, 2013Here are some screenshots to help clarify; maybe I'm missing something. In the Issue Permissions screen, you can see that the Assign Issues and Assignable User permissions are set to use error jira does the Users project role. Bigger version (http://www.flickr.com/photos/hookedbyesther/9917333125/) In the Project Role screen, you can see that the default group for Users is jira-users: Bigger version (http://www.flickr.com/photos/hookedbyesther/9917367026/) And on the People screen, you can see that JIRA Monkey, our project lead, is part of the jira-users group. (Bigger version http://www.flickr.com/photos/hookedbyesther/9917500853/) What am I missing that would allow us to have JIRA Monkey be the automatic assignee of tickets created?CommentAdd your comment...2 answers10-1Christian CzaiaSep 24, 2013Another idea: Are you using components? Maybe you're using components and the default asignee isn't your JIRA Monkey (default: component lead instead of project lead). CheersCommentEsther StromSep 24, 2013Yup, it was the components. Wow, how unintuitive. I can see how you might want to be able to set a different assignee for a specific component, but it seems to me that if you don't have anything specific set in a component, it should inherit from the project's default assigne