-
Suggestion
-
Resolution: Unresolved
-
0
-
4
-
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
Using GreenHopper, I am often changing the ranks and other features of issues, and every watcher of each issue is notified of every change. This has caused a large volume of JIRA notifications that makes them very easy to ignore. I'd like to have some filtering so I can determine which types of edit will trigger an Event (for instance, filtering out updates of a specific field).
- is related to
-
JRACLOUD-82675 [Tracked in Issue Links] Various notification-disabling feature requests
- Gathering Interest
-
JRASERVER-34232 As an Admin, I would like more granularity over the types of changes that trigger the Issue Updated event
- Gathering Interest
- relates to
-
JRACLOUD-81526 when creating new issue using automation with cloning attachment field then no issue updated event is triggered for attaching cloned attachment to new issue
- Closed
-
JRACLOUD-61654 Creating a sub-task should update the parent issue's "Updated date" or add an entry to the activity tab in viewing issue
- Closed
-
JRACLOUD-77371 Don't notify sprint change on issues
- Gathering Interest