we had an old project on which our employees should not be able to create issues. But they should be able to view the old issues, comments and so on.
So I created a permission scheme called "Archived Projects" and moved the project to this scheme. Originally, this scheme had the "Administer Projects" permission for the administrator group (which I'm part of) and the "Browse Projects" permission for the employee group.
Now everything works fine. Our employees can browse the old issues but not create new ones.
Problem: We still have some old issues within this project, which are currently on the state "Open". But we want to close them, so the assigned employees of these issues don't get a reminder e-mail twice a day.
So I gave myself (single user) permissions for resolving and closing issues within this project in the permission scheme.
But the problem here is that when browsing the issue, I can't see the buttons for resolving and / or closing the issue. They just don't appear.
The crazy thing here is that the Permission Helper states that I have all the permissions to resolve / close this issue. But I can't since I don't see the buttons to do so...
Any smart ideas on this?
Kind regards, Simon.
P.S.: In case you need the info: We're hosting JIRA 6.4.10 on our own servers.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
As part of the Bitbucket product team I'm always interested in better understanding what kind of impact the use of our tools have on the way you work. In a recent study we conducted of software devel...
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