This question is in reference to Atlassian Documentation: Managing global permissions
Article cites "Assign User" permission in the "Browse Users" paragraph. There is no such permission at the project level. There are two similar ones, but I don`t know which one is mentioned here. Is it "Assign issues" or "Assignable user"?
As the documentation says
Assign issues Permission to assign issues to users.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, that's what it says. Slightly different phrases can mean the same thing in English.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Maybe that's the problem. A project lead from our company wanted to assign users to his project. He couldn't do it without "Browse users" permission and that's why I looked up the documentation. In this context, "Assign users" looks great - you can assign them to anything. "Assign issue" is more exact, but not what I want.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ah, that's sort of misusing the word "assign" in English, and more-so in JIRA-speak.
Generally, you do not assign users to projects. It's an odd way of using "assign" in modern English. JIRA's use of language makes it even more strange - generally, when you use variations on the word "assign" when talking about JIRA, it's all about people and issues. Not the projects.
If you want to put/include/allocate users in projects, then the usual way to do it is to use the roles. People with "project administration" rights can add and remove users from roles in their project. Assigning issues has nothing to do with user maintenance (although you will want to put users into certain roles so that they can assign and/or be assigned, issues)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Please update your answer to include this information: "Assign users == Assign issues", if you don't mind.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Um, it already says that
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
anyone who has "Assignable user" permission can be assigned an issue in the project.
anyone who has "Assign User" permission can assign users to issues within the project.
Note: a user does not have to have the browse permission to be assigned issues. if you assign a user who does not have the browse permission, they will not receive notifications that you assigned them an issue. this is helpful when you are assigning work to a user who may not be using the tool.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
There is no such permission as "Assign user". There is "Assign issue" permission and "*Assignable* user". My question was related to the fact that the link text in "Managing global permissions" makes a weird combination of those two.
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.