Custom Assignable Fields in Notifications

Emily Brol November 11, 2024

We use the default assignee field in JIRA for the developer doing the work on an issue. We have a second custom assignable field called 'QC' for the person testing the developed work. 

I want JIRA to notify the person in the QC field when they are assigned an issue, the issue is edited, someone made a comment etc.

JIRA lets me add a custom field to a notification scheme however when I add the custom field QC to the 'you are assigned an issue' notification, the person in the QC field is not notified when they are assigned in the QC field.

When I read up on how to do this, it recommends either setting up a post-function or automation to notify the QC person. What is the best way to do this with the least amount of work to notify the person in the QC field when they are assigned an issue, the issue is edited, comments are added etc?

1 answer

0 votes
Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
November 12, 2024

Hello @Emily Brol 

What is the type of project you are using? Get that information from the Type column on the View All Projects page under the Projects menu.

I'm a little unclear on when you want notifications to go to the QC person. Do you want the specified events to send notifications to the person specified in the QC field all the time? Or do you change Assignee to match QC, and you want the notifications to be sent only when Assignee and QC are equal?

I don't think that a post-function would work in this case. Post functions are associated to workflow transitions. The post function would fire only when a workflow transition is executed which would not normally be the case for addition of comments, updates to a field, or issues are edited. 

If you choose to use Automation you would need to consider the limitations on how many automation rule executions are permitted per month for your subscription, and how adding more rules could impact that. You can find more information on those limits and how rule execution is counted here:

https://support.atlassian.com/cloud-automation/docs/how-is-my-usage-calculated/

When thinking about how many rules might be needed and how they would need to be constructed, I have questions:

1. When you say the QC person is "assigned" to the issue, do you mean when the QC field is changed, or do you mean when the Assignee field is changed to a user that matches the entry in the QC field? 

2. When you say you want notifications "when the issue is edited", which edits specifically do you care about? Do you mean when a change of any type occurs in any field? 

3. What information do you want in the notifications? Do you want different content depending on if the trigger was assigning the issue, commenting on the issue, or a different update to the issue?

 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events