Home > Unassigned Issues > Jira Error User Not Assignable

Jira Error User Not Assignable

does NOT have ASSIGNABLE permission" error10-1Esther StromSep 24, 2013I've looked around, and found answers that told me that this is most likely because my default assignee does not have the assignable permission (gee, thanks.) The problem unassigned issues are turned off is, the default assignee for my project DOES have the assignable permission. It's set

Allow Unassigned Issues Jira

via a project role, which the default assignee (also the project lead) is a member of. We do NOT want to

Jira Assignable User

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 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 assignee.CommentAdd your comment...10-1Jobin Kuruvilla [Go2Group]Sep 24, 2013You are not looking at the project role for the specific project but only at the default project role session. Go to the project and check under the roles tab.CommentEsther StromSep 24, 2013We're on 5.1. There IS no Roles tab under the project. The only way to get to Roles is from the Users dropdown in the top blue bar.Christian CzaiaSep 24, 2013The "roles" tab IS the "people" tab in 5.1. Your configuration looks right to me. Are you sure the permission scheme from your screenshot has been assigned to the project you are talking about? Esther StromSep

Assignee RED in this list, and elsewhere?10-1George CarvillOct 10, 2012It is not red in my live project. See the attached.project_leadproject-roleserrorCommentCommentAdd your comment...3 answers210vishwajeet singhOct 10, 2012You need to define permission scheme and https://answers.atlassian.com/questions/215496/the-default-assignee-does-not-have-assignable-permission-error make this user assignable, looks like by default project lead is not assignable in permission scheme. Please refer the following link on how to do the same https://confluence.atlassian.com/display/JIRA/Managing+Project+PermissionsCommentCommentAdd your comment...10-1DevendraJul 08, 2013Answers https://answers.atlassian.com/questions/94957/why-is-the-default-assignee-red-in-this-list-and-elsewhere provided by Janet and Vishwajeet are correct. I had the same issue and got fixed by the answers...CommentCommentAdd your comment...10-1Janet Albion [Atlassian]Oct 10, 2012Hi George, Ensure that the current Project Lead(eg: Brenda for project onBoard) has the Assignable User permissions for that project. Update us on your finding.CommentGeorge CarvillOct 10, 2012I will review roles again but I don't see where "Assignable User" permission is set.CommentAdd 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

User Functions JQLT Worklog Functions JQLT Links Functions JQLT Date Functions JQLT License JQLT FAQ Simplified Planner > J-Planner http://www.j-tricks.com/tutorials/permissions-based-on-workflow-status Installation J-Planner Configuration J-Planner Usage > Creating a plan Editing a plan Deleting a plan Viewing a plan Modifying a plan J-Planner FAQ Atla-Search Plugin > https://jamieechlin.atlassian.net/browse/JBHV-40 Atla-Search Installation Atla-Search Configuration Atla-Search Usage Atla-Search License Atla-Search FAQ Copy to subtask Plugin All Plugins License Request Plugin Store The Book About Us Feedbacks Contact unassigned issues Us Permissions based on Workflow Status 2/15/2011 209 Comments Ever wondered how to enforce permission checks based on workflow status? JIRA gives us a big set of options to restrict many of the operations (like edit, comment etc) on the issue or its subtasks depending on the issue status.Yes, I am jira error user talking about JIRA Workflow Properties. If you need to enforce a particular permission check at any stage in the workflow, all you need to do is to add the jira.permission.* property on the concerned workflow step. Following are the steps:Login as a JIRA AdministratorNavigate to Administration > Global Settings > WorkflowsCreate a draft of the workflow if it is active. Navigate to the step which needs to be modified.Click on the View step's properties link.Enter the permission property into the Property Key field. The property is of the form - jira.permission.[subtasks.]{permission}.{type}[.suffix] where:subtasks is optional - If included the permission is applied on the issue's subtasks. If not the permission is applied on the actual issue.permission - is a short name specified in Permissions class. Following are the permitted values as on JIRA 4.2admin, use, sysadmin, project, browse, create, edit, scheduleissue, assign, assignable, attach, resolve, close, comment, delete, work, worklogdeleteall, worklogdeleteown, worklogeditall, worklogeditown, link, sharefilters, groupsu

to the Adaptavist Product Support Portal http://productsupport.adaptavist.com. This instance will no longer be used and eventually shutdown. Any problems please raise an issue on https://productsupport.adaptavist.com/servicedesk/customer/portal/2 JIRA Behaviours PluginJBHV-40User does not exist message on assigningLog in PrintExport XMLExport Word Details Type: Bug Status: Closed Priority: Major Resolution: Duplicate Affects Version/s: 0.2.9 Fix Version/s: None Labels: None Internal Complexity: Unknown Internal Value: Unknown Description This issue has moved This issue has been moved permanently to Adaptavist's Product Support JIRA instance. All existing users of this instance should have the same username on our Product Support instance. However, you will very likely need to click on the Can't access your account link in order to reset to a new password. I am able to assign issues through the workflow and change the assignee on the edit screen. However when I use the assign option, taking me to http://jira.artirix.com/secure/AssignIssue.jspa, I get a message 'User charlie.lines does not exist'. Doesn't matter which user I select either, the same message is displayed. This only occurs on some projects within JIRA and the project setup is the same across the majority of my projects. Error in log: 2010-11-18 16:41:53,757 http-8080-3 ERROR charlie.lines 1001x17522x1 1y3xxdb 88.211.30.122,127.0.0.1 /secure/AssignIssue.jspa [webwork.util.ValueStack] METHOD: "fieldScreenRendererLayoutItemForField", exception: java.lang.NumberFormatException: For input string: "" Excerpt from log attached. I've checked the permissions and these users are assignable, they can all login and have access to the relevant project. On investigating further (with assistance from Atlassian) I looked back on recent changes and saw we had recently moved from 0.2.8 to 0.2.9 for this plugin in order to use hidden fields. The impacted projects all had behaviours mapped to hide a custom field - once I disabled the plugin the assign issue screen worked as expected. Not sure if I've missed something with the configuration but it feels like this is a bug. AttachmentsOptionsSort By NameSort By DateAscendingDescendingThumbnailsListDownload AllAttachmentsstacktrace_log.txt29 kB19/Nov/10 3:29 AMIssue links links to Product Support Activity People Assig

 
No related pages.