I have a saved filter that selects issues based on a custom field (requestor) = CurrentUser() and would like to setup a subscription to send the report to each user in the custom field. However, there is not a JIRA group with all the requestors listed to include in the subscription. Most of the requestors do not have a JIRA account so jira-users can not be used. Is there a workaround or a solution where a new group could be updated dynamically whenever a new requestor is added to an issue?
Updating the JIRA group can automated via the JIRA REST API but I'm not sure on what do you mean "whenever a new requestor is added to an issue". So this Requestor custom field is a list then? Is there any reason why you are not using the "Assignee" field here?
Requestor is a custom single user picker field that is required when an issue is created. The Requestor can be anyone in the organization and in most cases does not have a JIRA account (not enough licenses). Assignee is used to indicate which developer has been assigned to work the issue. Also, any suggestion on how the JIRA REST API would be setup? Thanks
I meant "Reporter" sorry, not Assignee. Try looking at the JIRACLI which simplifies the JIRA REST API so you can automate stuff like this. https://bobswift.atlassian.net/wiki/display/JCLI/3.6.0+-+Examples jira --action addUserToGroup --userId "testuser3" --group "testgroup2"
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 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