We use JIRAOD, and I have set up a bespoke permission scheme and removed Close Issue permission from all users bar one group (of which I am the only member). I have then added this permission scheme to a project, but every user (as far as I can tell) can still close Issues. I've even tried removing this permission from ALL members, groups etc., but to no avail.
Can you help me resolve, as this is a fundamentally important restriction for our business.
This has now been resolved (and Atlassian support were very helpful). However, as far as I can see, no changes were made - the set-up I have now (which Atlassian confirmed is correct) is, to the best of my knowledge, the same as before the problem was resolved. I suspect user error on my part, but can't identify where
I believe the resolution to this was that I had manually added some transitions to move to the "Closed" status, but that these weren't explicitly checking the for the relevant "Close Issues" permission. I had retained the default "Close Issue" transition for some steps, so as these default ones were set up correctly, users experienced the correct behaviour in some circumstances, but not all.
Easily solved once identified!
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
EaglePicher Technologies is a leading manufacturer of battery systems for diverse industries like defense, aviation, space or medical. As they operate in highly regulated industries, keeping a clear ...
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