Details
-
Suggestion
-
Resolution: Duplicate
-
None
Description
Similar to what we have for labels. Currently only ‘set' is possible. We should support this for all 'collection type’ custom fields.
Also group pickers, label custom fields, components, versions, request participants etc
Workaround
You can do this with https://docs.automationforjira.com/working-with-issue-data/advanced-fields.html#advanced-additional-fields (dead link, https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/ this appears to be a good replacement)
Trigger rule when value is added/removed from multi-select type field
One specific use case that comes to mind:
- Trigger: When Servicedesk participant is added to request
- Send e-mail to this participant
Could probably do some magic in the field value changed trigger, where if it's a multi-select type field (user pickers, labels, etc) we add an option to only trigger the rule if a value is added or removed. Then provided 'addedValues'/'removedValues' in smart-values.
Fields where this would be useful:
- Attachments
- Versions
- Components
- Participants
- Any other multi-select type field really
The smart-value should provide access to full details, so you can get the urls of the added attachments for example.
Attachments
Issue Links
- duplicates
-
AUTO-234 More ways to work with multi-select fields - ability to edit multi-value select field with all available options, Trigger/action to support 'add' & 'remove' on multi-select fields
- Gathering Interest