We want to build an issue type that allows a sub-set of our JIRA users to request additional permissions for all the other users in our system.
More specifically ... If the reporterA is a member of AA-Approvers, we want them to be able to request that any other user be added to AA-Admin, AA-ReadWrite or AA-Read. If a reporterAB is a member of AA-Approvers and BB-Approvers, there would be 6 groups they could add users to. Let's say we have a custom multi-select field called "Add to these Groups". In that mutli-select field are all of our groups. But when the ReporterA creates the ticket, in the create screen, we only want groups AA-Admin, AA-ReadWrite and AA-Read to be available for selection.
Does this make sense?
We know how to find which *-Approvers groups the reporter is a member of. What we're asking here is: how do we restrict the options in the "Add to these Groups" field?
All suggestions welcome.
We are still looking to solve this. We have a perl script that given a username will return all the groups that they have approver privileges for. We want all of those groups to be presented to the user in a JIRA ticket and let them choose one or more of them. So we call the script with user "kate" and it returns groups "AA-1" and "AA-2". Those are the only two groups that she can choose from when creating a ticket. Despite the fact that we may have hundreds of groups. Any ideas?
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