Could you explain what you mean by additional assignees? Jira issues only allow one assignee to each ticket. If you have created fields to act as additional assignees and I am assuming you are on Jira server as that is what is tagged here, you can update the notification scheme to include the user custom field and send on the same events that the assignee gets.
I just assumed that Jira had the default field of "Additional Assignees" since we cannot setup in custom fields through our company (using Jira server) due to policy restrictions. There is the Assignee field, that only allows for one person, but there is another default field that allows multiple "additional assignees" to be listed on an issue. I assumed that the same notification scheme would be used, but it does not. Where would I go to update the notification scheme? I may or may not be able to do that since we only have Project admin rights, not global admin.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I would suggest reaching out to your Jira admins on site. Explain that you want the same notifications that the assignee gets to also be sent to the custom field "Additional Assignees". They will need to update the notification scheme. If this is not possible, maybe create an automation in the project that adds the "Additional Assignees" as watchers of the issue. That should send out all the notifications if the notification scheme is similar to the default notification scheme that comes with Jira.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Unfortunately, anything that has to be done globally is almost always a no-go, so the scheme will most likely not be able to be updated.
I am working on the automation to set the additional assignees (or for us, customfield_10600) as watchers, but I cannot seem to figure out how to do it. I've tried the action "manage watchers" and adding the smart value {{customfield_10600}} in the add watchers field, but that errors out. I figured it can possibly be set in the edit issue action, under the "additional fields", using JQL, but can't figure that out either.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
A notification scheme can be set per project. So unless all the projects have to share all configurations, the easiest and best thing to do would be to update the notification scheme.
under the manage watchers action try this
{{issue.customfield_10600}}
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Tim...I was testing this out in UAT, which was what was causing my problem. The customfield in UAT is 10900, not 10600, which is in Prod, so that worked! I'm hoping this is a temporary work-around, because just updating that notification scheme would be best, but it looks like I do not have the permission to update that, even though I am a project admin for the project. That's a separate issue though, so thanks for your help with this one!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Are you saying that when the issue is reassigned the new assignee does not get notified?
Thanks,
Kian
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
No, when an automation rule that creates an issue is triggered, it sends to the "assignee", but not to the "additional assignees", which is a field we have, that I had assumed was a default jira field, since we cannot create custom fields at our company.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.