In the projects-menu an d the projects page all projects are listed to every user, whereas in the dropdown menu of projects jira gives me when creating an issue, it shows me only those projects I have permission to create issues in.
I am aware that the project list is more difficult to differenciate since the user could have viewing rights, creating rights and so on, but I really need to reduce the overwhelming number of projects our users get to see in the projects page. Plus: I still believe I just must have missed the right spot and it should be quite easy to set up...
The projects under projects menu uses the "Browse Project" permission whereas the Create uses "Create Issue" permission. You will have to manage it under project permissions.
Remember, if you have viewing rights, it will appear in that lst for sure.
Thank you, that helps a lot since I thought the "browse project" permission would only target the search / filter functionality.
But it brings me to the source of the problem: in the "browse project" permission we have both "custom userfield" and "author" set up - we automatically put all of our support mails into jira and want the users to be able to watch their raised issues and to put in other names (of their boss, for example) of people who they give the permission to watch their raised issue too.
And it seems as though the rule " if you have viewing rights, it will appear in that list for sure." ist more of a " if you might have viewing rights, it will appear in that list for sure.", since not only those projects the user has an issue in, which he raised and therefor (author) can see / browse but all of the projects with the permission to author are shown.
The proble here is JIRA doesn't know whether it should show the projects selectively or not. You have defined that anyone who is an author or in the user custom field can see this project. And the users are in those irrespective of whether they created a ticket in that project it seems?
Yes, it seems that Jira can't see at the point whether or not the user has an issue in the project or not. I have no idea how to resolve this. I need the users to be able to see their support issues no matter in which project they are, but I also need to reduce the visible projects.
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