Hi,I've got an important question about the right way to distribute permissions for customers at JIRA. I try to describe our problem as well as i can do: We work with our customers directly in JIRA, they have Permissions to create and assign issues or even schedule isues. For this we created a standard permission scheme with different project roles and different permission for our customers, like:- Project Role "Customer employee"- Project Role "Customer Project Manager" and so on..Then we add our customers under "People" and the project role at the affected Projects, so they can work with us. Another important point is that our customers can use the @-mention feature. So they can easily mark our consultants at issues or something else. To be able to do that we have to give them the global permission "Browse users and groups", otherwise they cant mark / see our users. Everything is fine, they can use the @-mention Feature for example at the comment section and they can only see our employees and no other customers. The same applies for the assignee, they can only see our employees and colleagues from the project. So far so good, but here is our big problem. If they use the button "view all issues" under "Search" Panel at the left, they can filter about the right assignee at the search page.But here they can see every user and every group in the whole Jira System?! Just with typing an "e" or any other letter? so did I do something wrong? Or is this by design? Or a Bug? Regards,Jonny

Community
Q&A
Jira
Questions
Understanding question about Global Permission "Browse Users and groups"

Issues which are in Done category are showing in incomplete issues in active sprint board

Issues which are in Done category are showing in incomplete issues in active sprint board.

Also, The Done column is in the right end and all complete issues status are mapped to the column and still issues showing as incomplete.

Please help

1 answer

1 accepted

1 vote

Answer accepted

It seems to be an open issue which has been declined by Atlassian as won't fix since it didn't gather much votes.

https://jira.atlassian.com/browse/JRASERVER-34165

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

For cloud instance - https://jira.atlassian.com/browse/JRACLOUD-34165

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi Tarun,

Thanks for your reply. I've already seen this two suggestions, but i think its only nearly the same problem.

Our customers are not annonymous and everything is working fine with the @mention Feature and choose an Assignee.

It's only the assignee button at the global issue search filter that are not working properly.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hello @Jonny Klaas

In the JIRA ticket, Anonymous is just used as an example, basically if you have some projects configured for public access then public/anonymous users can see the list of all users in the issue navigator view by clicking on the "Assignee" button pretty much same as in your case. Since you have some customers mapped for read access to Project X but in the issue navigator view those customer will be able to see the complete list of users in the assignee section even if they are not in the same project as the logged in customers.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi Tarun,

Thanks for the detailed explanation, i got it now.

But it's pretty annoying that atlassian does not want to fix it,because it's a really big privacy problem.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hello @Jonny Klaas

Indeed this is an issue, may be you can add a comment on the ticket so that Atlassian might re-open the ticket. Atlassian implements lot of new features in every release but features are picked on various factors and one of those factors is the user votes. And since this particular feature didn't get much user votes thus it wasn't picked.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Here's the policy -

https://confluence.atlassian.com/support/implementation-of-new-features-policy-201294576.html

If you feel my answer has helped you then please accept/upvote the answer. thanks.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Forums

Q&A

Community resources

Support

Top groups

Community resources

Support

Learn

Community resources

Support

Events

Community resources

Support

Issues which are in Done category are showing in incomplete issues in active sprint board

1 answer

1 accepted

Suggest an answer

Was this helpful?

Thanks!

TAGS

Community showcase

Atlassian Community Events