Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JRACLOUD-14317

Notifications: Separate Issue Created from (new) Sub-Task created

    XMLWordPrintable

Details

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

    Description

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

      I think this issue should be part of resolving [#JRA-9941] new notification type for "Sub-task of issue created" but if it goes faster I would really prefer to have the standalone fix:

      We have a notification scheme which informs every developer about new issues in a project. This is nice as it is easy to keep track of new issues or add comments if you know more about it.

      But there is a problem: As Issue Created notification also applies to Sub-Tasks the developers get a huge heap of unwanted notification mails.

      This is because we use Sub-Tasks as a way a developers might organize their work to document step by step approach. Thus most of the time such sub-tasks are more like private todos than anything interesting to the public.

      I suggest to have a separate notification called Sub-Task created which is independent from Issue created.

      If resolving JRA-9941 it might still be good to have the two notifications introduced here just in case you want to simulate the old behavior, i. e. getting Sub-Task created mails just as Sub-Task for Issue created (as proposed by JRA-9941).

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              2f5ffb0094a7 Mark Michaelis
              Votes:
              4 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: