Here's our need: For any given issue, a lead engineer might decide the issue needs additional required reviewers. This list of people is to be picked from a group called Review Board Members. Once all those people listed as required reviewers have given their input (which includes Approve/Declining the resolution, and their comments), the lead gets notified.
So parts of this I have, pretty much all done through ScriptRunner. I have:
- the Review Board Member group and the appropriate edit permissions when the issue is in the Needs Review state
- a screen that contains fields for Accept/Decline, and a Review Comments field. When the user gives their input, I capture that and put it into a read only field showing the user name and what their input was
- Email sent when everyone in the RBM group has given their input
But for most issues, only a subset of the RBM will need to review the issue. I know JIRA can limit a single selection user list based on group, but this functionality doesn't exist for multiselection list. If it did, that would be perfect.
So I thought maybe a Checkboxes or multiple choice Select List, but I can't figure out how to populate those fields with the users of a group (doesn't seem to be an option to script up the values).
I also thought using the Vote capabilities would be a nice way, but you can't really add your own vote comment, and you can't specifically choose who needs to vote on an issue unless I gave the lead engineers permissions to modify project permissions to swap out who can vote on an issue, and that wouldn't be per issue anyway.
Does anyone have a suggestion on how to approach this? I'm trying my best not to have to create our own plugin for this, but starting to look like that might be needed. Hopefully I'm just missing something obvious!
Ha, found my own answer probably.
Using ScriptRunner, I can populate the field with the users from the RBM group, checking if there is a current selection and if so, set the selection to that. That will allow the script to populate the field each edit, but maintain selection state.
Does that sound like the best approach?
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
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