It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Anonymous users can close issues even though the permission helper says otherwise

We have configured a lot of our projects to have anonymous read access to issues, but not to be able to write or change. Now, we accidentaly found out that anonymous users can actually Close issues and I verified with two issues. Now, when I use the Permission Helper, testing with the fields:

User: (none selected)
Issue: the one that I just closed as anonymous (JAVAAPI-27
Permission: Close Issues

The Permission Helper then returned:

<dl><dt>Permission name:</dt><dd title="Close Issues">Close Issues</dd></dl><dl><dt>User:</dt><dd title="Anonymous">Anonymous</dd></dl><dl><dt>Project:</dt><dd title="Java API">X</dd></dl><dl><dt>Permission scheme:</dt><dd title="blah">XYZ Permission Scheme</dd></dl><dl><dt>Issue:</dt><dd title="JAVAAPI-27">X-27</dd></dl><dl><dt>Status:</dt><dd> Anonymous does not have the 'Close Issues' permission</dd></dl>

and also:

"Anonymous users cannot satisfy this condition, the only condition Anonymous users can satisfy is the 'Anyone' group.".

To me this seems like a bug, but is there something obvious missing?

This is JIRA 6.0.5.

1 answer

1 accepted

2 votes
Answer accepted
Nic Brough Community Leader Feb 10, 2014

Ah. The permission helper only tells you about permissions. Which are a set of flags to be used in other places in the system. A lot of this flag usage is hard-coded and obvious (allow worklog delete, allow issue create, etc), but some are more nebulous because the users can configure how they get used.

The most obvious cases are "issue resolved" and "issue closed". These do NOT do what you think they do automatically, their use is configured. If you look at the default workflow, you will see perfectly logical uses for them, set up as "conditions". Such as "user can only use the resolve transition if they have the resolve permission"

But Jira doesn't know that you want to do this sort of thing automatically. Imagine you set up a workflow that has a transition from "open" to "wombled" with a name of "wombling on" - Jira can't possibly know that this should only be done by people with "resolve" permission.

What I'm heading to is "you need to add conditions to your workflow in order to make these permission flags work the way you're expecting"

Thanks. This solved the problem. The root cause of this was that the workflow had a accidentaly a duplicate transition for "Closed". So, deleting that and reusing the standard one solved the problem.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted in Portfolio for Jira

Program managers, we need your help! We want to learn about how you plan work for a team of teams

Hi community members, My name is Erika and I’m a product manager at Atlassian. We’re currently investigating how teams are planning work at the program level. We understand that every team in a tea...

87 views 0 4
Join discussion

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you