Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Version From version 1.3.162 removed , the jemhIncludeIssueHeader Velocity macro found in templates based on the “Generic” and “Jira” themes has been modified. This macro no longer renders the jemhIncludeUserRole macro, which is used to display the notification recipient’s role in the related issue from notifications. This was done to reduce message plan consumption by making default templates less recipient-specific. This in turn means it is more likely JEMHC can notify multiple users with one email (when using BCC recipient mode).

...

.

How does this impact my configuration?

If you are using a default template provided by JEMHC, or are using a custom template that calls jemhIncludeIssueHeader then a Jira user recipients role (e.g. Reporter, Assignee) will no longer be rendered in the notification.

Why has this change occurred?

Rendering recipient-specific information (such as issue role) means that JEMHC can’t send the same email content to multiple Jira users when “BCC” recipient type is chosen in the notification mapping. Therefore, it had to send a separate message for each user with a unique role. With this change, most customers should see a reduction in the amount of messages consumed from their plan.

How do I get roles in notifications again?

Inserting the below macro may increase message usage as it adds recipient-specific content.

If you need the recipient user’s role to appear on notifications, this can be done by using a custom template. Create a template based on the Jira or Generic theme, and insert #jemhIncludeUserRole() in the desired location. For example, in an HTML template :

Code Block
languagehtml
<span class="your-role">#jemhIncludeUserRole()</span>

...

based on the default (see lines 8-12):

Code Block
#@issueNotification()
<table id="background-table" cellpadding="0" cellspacing="0" width="100%">
    #jemhIncludeStandardActionHeader()
    <tr>
        <td id="email-content-container">
            <table id="email-content-table" cellspacing="0" cellpadding="0" border="0" width="100%">
                #jemhIncludeIssueHeader()
                <tr>
                    <td class="email-content-main mobile-expand  wrapper-special-margin">
                        #jemhIncludeUserRole()
                    </td>
                </tr>
                #jemhIncludeIssueDetail($serviceJiraFields)
                #jemhIncludeBody()
                #jemhIncludeDirectiveSetLinks()
                #renderCustomerSatisfaction()
                #jemhIncludeAddComment()
                #jemhIncludeFooter()
            </table>
        </td>
    </tr>
</table>
#end
#inhibitSendingConditions()

Then when a real notification is sent, recipients with a role in the issue will have their role displayed. For example:

...

Filter by label (Content by label)
showLabelsfalse
max5
spacescom.atlassian.confluence.content.render.xhtml.model.resource.identifiers.SpaceResourceIdentifier@957
sortmodified
showSpacefalse
reversetrue
typepage
cqllabel in ( "templates" , "notifications" , "velocity" , "role" ) and type = "page" and space = "KB"
labelsnotifications templates velocity role

...