| Name | Set security level based on group |
|---|---|
| Version | 1.0 |
| Product Versions | JIRA 3.4+ |
| Author(s) | Rodrigo Borghette Schmidt |
| Homepage | Set security level based on group |
| Price | free! |
| License | BSD |
| JavaDocs | |
| IssueTracking | |
| Download JAR | https://svn.atlassian.com/svn/public/contrib/jira/jira-security-level-plugin/jars/jira-security-level-plugin-1.0.jar |
| Download Source | https://svn.atlassian.com/svn/public/contrib/jira/jira-security-level-plugin/ |
Description
A workflow postfunction it sets the issue security level based on one group the reporter is member of.
The group and security level have both the same name and in order to make this work as we expect, the user cannot be member of more than one group that has the same name of a security level.
For our convenience, we decided to add a leading "#" to the security level name, so that we can control when the plugin should act or not. So, the group and security level names must be the same, except that the security level name has a "#" at the beginning. If you have any doubt, please let me know.
Installation
- Download the jar and place in your webapp's lib folder
- Restart JIRA
- Add the post function to your workflow step(s)
Usage
Example
We've been using this here to automatically set the issue security level for one of our projects according to the geographic region our customers are located. For example, if we have a customer in US, he is member of a group named US and there is a security level named #US. If he is in Latin America, another group called LA and a security level called #LA and so on. In this way, when he creates an issue, he does not need to have set security level permission and customers from other regions won't see/mess with his issues.
Version History
| Version | Author | Notes |
|---|---|---|
| 1.0 | Rodrigo Borghette Schmidt | Initial release |
Screenshots
Screenshots |
|---|
| There are no images attached to this page |

Comments (16)
Aug 09, 2006
Neal Applebaum says:
Thank you for contributing this. I think this alone makes JIRA usable as a helpd...Thank you for contributing this. I think this alone makes JIRA usable as a helpdesk tool. I do have one question - is it mandatory that the security level be named with a "#"? I tried naming the Security level exactly the same as the User Group, but it didn't work that way.
Feb 14, 2007
Rodrigo Borghette Schmidt says:
Hi Neal, Yes, it is necessary to place a "#" at the beginning of the security l...Hi Neal,
Yes, it is necessary to place a "#" at the beginning of the security level's name. In order to modify this behaviour, it is necessary to change the source e rebuild the plugin.
Jun 02, 2007
Henry Zhang says:
I have test this plugin under jira 3.9, it did not work!I have test this plugin under jira 3.9, it did not work!
Jun 02, 2007
Neal Applebaum says:
Oh, that's not good. This plug-in is crucial to my implementation of JIRA (I am ...Oh, that's not good. This plug-in is crucial to my implementation of JIRA (I am still on 3.6.5)
Jul 04, 2007
Ákos Diviánszky says:
We had the same problem here, the plugin was not working under 3.9. Changing the...We had the same problem here, the plugin was not working under 3.9.
Changing the max version string directly in the jar file solved the problem.
Aug 09, 2007
Simone Kaiser says:
We upgraded from release 3.7.1 to release 3.10 and the plugin does not work any ...We upgraded from release 3.7.1 to release 3.10 and the plugin does not work any longer. How do I change the max version string in the jar file? Which variable is it? Which steps have to be done?
Sep 26, 2007
mameha says:
I updated that variable (to version 9.9) but the plugin still does not work in J...I updated that variable (to version 9.9) but the plugin still does not work in JIRA 3.9
FYI, the variable is amended by unpacking the .jar, then amending the line in atlassian-plugin.xml then repacking the .jar and installing in JIRA's WEBINF/lib as usual.
If anyone cracked this please post the answer.
Sep 06, 2007
MehmetM says:
It's the working copy for 3.9, 3.10. I wrote it as Listener and I've add some fu...It's the working copy for 3.9, 3.10. I wrote it as Listener and I've add some functionalty (prefix can be defined and projects can be defined)
Sep 09, 2007
Aggelos T. Paraskevopoulos says:
Mehmet, is there a potential problem with implementing this as a listener, I me...Mehmet,
is there a potential problem with implementing this as a listener, I mean you risk of sending notifications to users that after changing the security level won't be allowed to see the issue? I'm not sure in what order the event listeners are fired, so if the notification (e.g. MailListener) takes place before the auto security level listener, emails are sent without respecting the visibility of the issue.
Sep 10, 2007
Emily Stumpf says:
I tried this with 3.10 and it worked fine (the original, not the Listener one).I tried this with 3.10 and it worked fine (the original, not the Listener one).
Oct 19, 2007
William Chever says:
Rodrigo, Thanks a lot for this! This solves a critical issue in our e...Rodrigo,
Thanks a lot for this! This solves a critical issue in our environment.
Bill
...
But in using it, I figured a way to accomplish the same thing easily. We are using 3.10.
We have a field called Account Name set up as a group picker. Create one security level, make it the default and add to it your internal support group, and then add to it the Group Selector option and select the Account Name field. All users in a particular group can see all their own issues, but no one else's, and your internal support group can see everything. No need for the plugin or maintaining the various security levels when adding a group.
Bill
Nov 19, 2007
Joshua Goodall says:
Is that issue.store() actually required? Surely com.atlassian.jira.workflow.func...Is that issue.store() actually required? Surely com.atlassian.jira.workflow.function.issue.IssueStoreFunction takes care of that for you for every transition anyway?
Jan 03, 2008
Tom Clarkson says:
Hey guys, this is great work! Has anyone tried setting the security in a po...Hey guys, this is great work!
Has anyone tried setting the security in a post workflow function based on component? How different it would be from this function?
We have users who can be in multiple groups and this function cannot determine which security level to assign because they are in more than one group.
If the security could be set based on the component, it would not matter how many groups a user was in - the security would work.
Cheers, Tom
Jan 17, 2008
Emily Stumpf says:
Does anyone know if this plugin has been updated to deal with the index changes ...Does anyone know if this plugin has been updated to deal with the index changes of [Jira 3.11|http://confluence.atlassian.com/display/JIRA/JIRA+3.11+Release+Notes]?
Thanks!
Emily
May 06
Erin says:
Has this been tested with 3.12.3? I'm getting this exception when I click "Crea...Has this been tested with 3.12.3? I'm getting this exception when I click "Create Issue" for projects which use this function on the initial "Create" transition. It does create the issue and set the security level correctly, it just throws this error as well.
Jul 24
Michele Tuveri says:
It works fine in my environment with Jira 3.12.3 That's what I noted: the plug...It works fine in my environment with Jira 3.12.3
That's what I noted: