Page Comparison

...

• user stops watching an issue(s)
• reporter of an issue changes
• an issue gets assigned to a different user
  • that user starts getting email notifications
• another user is set as project lead in that JIRA project
• user is inactive in JIRA
• user is not allowed to see the change according to the level of visibility (e.g., if comment added to JIRA issue can be seen only to a specified group of users in JIRA)

Open your JIRA User Profile → Email Digest menu to configure your personal digest settings

The page will show how many notifications is already in the digest, allow you to preview the digest and tell the system to send Email Digest immediately.

In addition, you can change whether the plug-in should send digest to you, time slots in a week to send digest and the maximum limit of the amount of records in it.

Image Removed

Email Digest

You will receive digest email at a scheduled date/time if there is at least one update happened in JIRA where you are the watcher.

If there were no updates in JIRA then the digest email will not be sent.

...

Actions Recorded in Digest

Email Notifications Digest sends an email based on the actions recorded from JIRA updates.

The actions recorded in digest are:

• Create new issue
  • all issues types are supported
• Updates to an issue
  • all modifications made in issue fields
    • standard fields
      
      • description, summary, component, affects/fix versions, issue assignee/reporter, due date, attachments etc.
    • custom fields
      • labels, planned start/end dates, user picker, group picker, checkboxes etc.
• Comment to an issue

  • add / update / delete comment

    Info
    If user is not allowed to see a comment due to visibility level restrictions (comment cannot be visible to JIRA group user is part of), record will not be sent in a digest.

    
    

• Move an issue

• Convert an issue to task / sub-task

• Delete an issue