The problem here is perfomance. To implement this feature properly, we need an efficient way to determine whether the user has issues assigned to them or not. Performing a search for each permission check will cause the system to slow down significantly,especially since permission checks are performed constantly.

A workaround that we gave the users for JRA-4935 was to have a special permission where projects were only visible if the user also had the "create issue" permission. We can do a similar thing here and display the project if and only if the user has the Assignable permission.

That way only users who could have issues assigned to them will be able to see the project, even if they do not have issues assigned to them at the moment. Will this be acceptable for now?

Cheers,

Mark C

Yes, that would be an acceptable solution for now.

Thanks,
Erik

You will need to copy the file CurrentAssigneeHasAssignablePermission to the path \com\atlassian\jira\security\type in your JIRA install and add the lines below to your permission-types.xml and restart JIRA.

<type id="assigneeassignable" enterprise="true">
    <class>com.atlassian.jira.security.type.CurrentAssigneeHasAssignablePermission</class>
</type>

You can now choose a "special" permission type that will hide the projects if you don't have ASSIGNABLE permission.

Let us know how you go with this.

Cheers

Mark C

Thanks for the quick turnaround on this one. I'm eager to get this into our system, but I'm swamped right now. I'll let you know how it works for us, when I get a chance to plug it in to our system.

Thanks again.
Erik

That's no worries, I'll resolve this issue for now (we're trying to clear out 3.5 issues). I've tested it locally and it seems to work as stated fine. Feel free to reopen the issue if you have problems with it once you get a chance to patch it.

Cheers,

Mark C

admin.permission.types.current.assignee.has.assignable.perm

It would be nice if that was cleaned up.

Also, I've checked it out on our system and functionally it works as we need it to. Thanks again for the quick turnaround.

Apologies for the oversight! The actual title should be "Assignee (show only projects with assignable permission)". The process is slightly complicated if you want to change this in your installtion. You'll need to unzip the jar language_default.jar, find the file JiraWebActionSupport.properties and add the line below to it.

admin.permission.types.current.assignee.has.assignable.perm = Assignee (show only projects with assignable permission)

You should then rezip the JAR and replace the old language_default.jar with the new one. The somewhat complex process is to due the fact that JIRA can be internaltionalised into other languages.

The name is unimportant other than for administrative purposes, so if you don't want to go through the trouble of uodating the properties file, you don't have to. It will be fixed in JIRA 3.5

Cheers,

Mark C

Forgetting the current implementation, what I'd like to see as a customer is a General Configuration setting called "Advanced Permissions" or something. If we set that to on, then these more granular permissions become available. Then, when we upgrade, the configuration setting follows us.

Please advise if I am correct in that upgrading means changing the .xml file again.

Thanks.

Thanks,
Dylan