NOTIFICATIONS Flashcards
Issue subscription problem:
View issue but get empty email.
Possible causes:
All issues are resolved when issue jura executes subscription job
Setting to send email even if JQL returns empty results.
Filter subscription can:
Use a cron expression to schedule.
Set only one recipient at the time (group or self)
Require browse projects permission to be made ! (If they loose it filter will be hidden)
Team managed receivers of notifications:
All watchers
Current Assignee
Reporter
Current user
Project Lead
Project role
Permissions needed to configure notification scheme:
Jira administrator global permission
Permissions needed to configure notifications:
Project Administrator
Notifications for Jira comment deleted:
Doesn’t exist it sends an issue updated event
Notification recipients (company)
Current assignee
Reporter
Current user
Project lead
Component lead
Single user
Group
Project role
Single email address
All watchers
Custom field
Group custom field
Default notifications:
You’re watching the issue
Reporter
Assignee
Mention
( Personal preferences can be changed)
Notifications will not be sent if:
User doesn’t have browse project permissions
Is not a member of any issue security applied
Email formatting setting in default user preferences:
Text
HTML
Notifications can be triggered by:
Filter subscription
Automation rules
Events like edits @. Etch…
Email from Jira administration
Team managed notifications events that aren’t possible:
No custom events
No events tied to post functions
Default recipients for notifications:
assignee
reporter
all watchers
Personal notifications settings cannot impact notifications from:
Filter subscription
Jira admin emails
Announcements
Automation rules
Third party apps
Mail handlers: creating an issue through email
New issue is created if email does not have an existing key
If it does comment is added to the existing issue