We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.

    • Icon: Suggestion Suggestion
    • Resolution: Duplicate
    • None
    • Scheduled Tasks
    • None
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      Here's an issue we're running into. People will often make a lot of sequential changes to a bug, and depending on whether or not the workflow screens directly support doing all those changes at once, subscribers to change notifications may get blasted with emails that are all related to the same bug.

      Example: someone writes up a bug, goes back and edits a custom field that wasn't on the bug creation screen, attaches a screen shot, then assigns it to someone. Anyone subscribed will get four emails for one bug being created.

      Suggestion: have Jira wait x minutes on the most recent change to an issue to let it "settle" before sending out a notification email, and have that email contain all the changes at once.

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.

              • Icon: Suggestion Suggestion
              • Resolution: Duplicate
              • None
              • Scheduled Tasks
              • None
              • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

                NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

                Here's an issue we're running into. People will often make a lot of sequential changes to a bug, and depending on whether or not the workflow screens directly support doing all those changes at once, subscribers to change notifications may get blasted with emails that are all related to the same bug.

                Example: someone writes up a bug, goes back and edits a custom field that wasn't on the bug creation screen, attaches a screen shot, then assigns it to someone. Anyone subscribed will get four emails for one bug being created.

                Suggestion: have Jira wait x minutes on the most recent change to an issue to let it "settle" before sending out a notification email, and have that email contain all the changes at once.

                        Unassigned Unassigned
                        46dd16050868 Scott Bilas
                        Votes:
                        55 Vote for this issue
                        Watchers:
                        34 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                            Unassigned Unassigned
                            46dd16050868 Scott Bilas
                            Votes:
                            55 Vote for this issue
                            Watchers:
                            34 Start watching this issue

                              Created:
                              Updated:
                              Resolved: