|
History
| Log In
|
|
|
|
I created this issue because I thought this functionality is something any who use custom workflows may wish.
As far as hacking JIRA's PermissionManager, this information may be interesting, but not necessarily something I will be permitted to do in this organization. Scott,
I now have JIRA Enterprise 3.1.1 and the source code. I did a JIRA presentation for our business managers, and one thing that stood out was the long list of users and the chance of accidentally assigning an issue to a user who is not in the restricted conditional group roles as defined in our workflow. Theres a hack from Atlassian, see http://confluence.atlassian.com/pages/viewpage.action?pageId=118605
 Hi Joshua,
Let us know if you need further information on this or if the referenced document addresses your requirements. Regards, My managers don't feel very comforted when I ask to implement a fix that includes the word "hack". Is this functionality something that is seriously being considered in the future of JIRA?
This plugin is certainly a step in the right direction. One of the areas where we have the most problems is when those with permissions to assign accidentally assign an issue to someone in a different group/role who does not have permissions to assign using "Assign" under "Operations". The problem is, this plugin addresses the assignee list at the Step level, and not the Transition/Action level. A given Step in a workflow may have Transitions/Actions that go to different groups, such as business owners, development managers, QA managers, developers, release engineers, QA engineers, etc.. Someone in a specific group/role should only be able to assign to someone in the same group/role if they are using "Assign" under "Operations". However, if they click on an "Available Workflow Action" that allows assignment, they should be able to Assign to the group/role specific for the resulting state to that action. Thanks for your help, We are considering including this functionality in a future version of JIRA. As this issue has not been scheduled yet, unfortunately I cannot provide an accurate time line for its implementation.
The plugin is labeled a 'hack' as it relies on manually adding properties to step definitions in the workflow. When we include this functionality in JIRA we might change the way it works. The source to the plugin can be found here: So if you like you can customise it to your needs. Thanks, On the plug-in page they say: "broken and deprecated."
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Improvement
Open
Minor
Limit "Assign To" list to specific user group
This is not possible out of the box, but would be possible with some hacking of JIRA's PermissionManager.
Are you a java programmer?