Invalid license: Your Refined is only licensed for 10 users.

Versions Compared

Old Version 3

changes.mady.by.user Vlad

Saved on

compared with

New Version Current

changes.mady.by.user Vlad

Saved on

Key

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

Problem: How to create a notification configuration that would send out digest of changes and comments in issues happened since yesterday?last run of this notification?

Here's how you approach it in Raley:Solution


1) Create a new Notification configuration of type "Jira issues digested messaging". 

...

3) Now you specify a JQL rule that will be used as a filter for issues. Only those which match against it will be included into the digest.  Use Jira issue navigator to make the JQL rule easier.

4) Specify subject of the email. 

...

5) Specify recipients using TO, CC and BCC fields. You can use a mix of values picked from combo-box'es and free-text expressions. During notifications configuration execution all issues will be grouped by recipients.For example, if you have 10 assigned issues and 3 different assignees, then system may send 2 issues to assign A, 3 to assignee B and 5 to assignee C. Which assignee will receive which issue will be resolved automatically  

Recipients will be calculated as following:

a) For given list of issues retrieved according to JQL, resolve all recipients emails based on recipients codes specified in TO, CC, BCC combos. 
b) In addition to recipients found in a), add recipients defined in free-form text/expression for TO, CC and BCC textboxes to each issue
c) Create sending groups: each containing TO, CC, and BCC email addresses AND list of issues to be sent with that group
d) If Send As = "Single Email", then sent out those groups, each group at a time
e) If Send As = "Multiple Email", then split each sending group into small groups where each subgroup has exactly 1 email address (TO, CC or BCC) and the same set of issues as parent group. Send those subgroups, 1 group at a time.


6) Finally, specify a message template. You can use our Template Wizard to simplify simplify generation of the template, just make sure you use Table layout so, issues will be shown as HTML table.

Here's a little example on how to render both, changes made and comments added since the last run of this notification configuration. 

No Format
#foreach ($issue in $issues)
  #foreach ($history in $issue.changelog.histories)
     #if ($jirassimo.isAfter($history.created, $context.yesterdaylast_run))
        #foreach ($item in $history.items)
            $item.field was changed from $item.fromString to $item.toString
        #end
      #end
  #end
 
   #foreach ($comment in $issue.fields.comment.comments)
      #if ($jirassimo.isAfter($comment.created, $context.yesterdaylast_run))
        Comment by $comment.author.name: $comment.body
      #end
   #end
#end


You probably noticed the usage of $context.last_run variable. This variable contains the datetime of last invocation of Scheduled notification configuration, no matter whether there were any emails sent with that invocation or not. 

The value in $context.last_run is stored in format yyyy-MM-dd HH:mm and you use $jirassimo.isAfter() helper function to understand if a date in argument 1 is after the date in argument 2.


There are more variables available in $context. To learn about them take a look at Context variables wiki page. To learn more about functions available in $jirassimo check out this page