Uploaded image for project: 'JIRA (including JIRA Core)'
  1. JIRA (including JIRA Core)
  2. JRA-5493

Ability to add watchers during issue creation

    Details

    • Feedback Policy:

      JIRA feedback is collected from a number of different sources and is evaluated when planning the product roadmap. If you would like to know more about how JIRA Product Management uses customer input during the planning process, please see our post on Atlassian Answers.

      Description

      Atlassian Update – 31 December 2015

      Hi everyone,

      Thanks for voting and commenting on this issue. Your feedback is key to helping us understand how you use JIRA so we can continue improving your experience. We have reviewed this issue over the last few days; however there are not currently any plans to implement this suggestion.

      Please make sure to check out:

      Another alternative is to use "@mentions" in the description of an issue to notify end users about the issue being created, and the recipients can then decide if they want to watch the issue.

      Please remember that jira.atlassian.com is one of many inputs for the JIRA roadmap. You can learn more about our process here.

      I understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions.

      Regards,
      Dave Meyer
      dmeyer@atlassian.com
      Product Manager, JIRA Platform

      Original request description:

      As a Project Manager I want to make sure that respective team members (including me) are informed about new issue creation and depending on an issue type are automatically added as watchers. I want this to action to become inseparable from issue creation, so that the original issue reporter does not have to inform anyone about issu creation manually. I want to be able to control the watchers' list and nominate the users.

        Attachments

        1. logerror.txt
          30 kB
        2. mention.png
          mention.png
          36 kB

          Issue Links

            Activity

            Hide
            pub159031616 Patrick Wolf added a comment -

            @JoRhett: Looking at the description above the Jira Watcher Field doesn't work in the cloud.
            > a free third party plugin JIRA Watcher Field for JIRA Server customers.
            > a free Atlassian Labs plugin JIRA Autowatch for JIRA Cloud customers.

            So there is effectively no solution for the cloud as the JIRA Autowatcher doesn't fulfill the very basic requirement of choosing who should watch the ticket.
            By the way this ticket was created on "13/Dec/2004 7:32 PM" and is close to 12 years old. I have trouble believing that something so basic hasn't been addressed for that long.
            Which brings me back to the question: "if its through lacking of caring about their users or if they are drowning in technical debt for way too many years."?

            Show
            pub159031616 Patrick Wolf added a comment - @JoRhett: Looking at the description above the Jira Watcher Field doesn't work in the cloud. > a free third party plugin JIRA Watcher Field for JIRA Server customers. > a free Atlassian Labs plugin JIRA Autowatch for JIRA Cloud customers. So there is effectively no solution for the cloud as the JIRA Autowatcher doesn't fulfill the very basic requirement of choosing who should watch the ticket. By the way this ticket was created on "13/Dec/2004 7:32 PM" and is close to 12 years old. I have trouble believing that something so basic hasn't been addressed for that long. Which brings me back to the question: "if its through lacking of caring about their users or if they are drowning in technical debt for way too many years."?
            Hide
            jorhett Jo Rhett added a comment -

            Again, your comments are valid but cloud didn't exist when this was opened and everything described in the issue type is provided by the free plugin. So the length of this issue isn't relevant.

            I totally agree about their lack of support to important issues. I think you're harping on the wrong one.

            Show
            jorhett Jo Rhett added a comment - Again, your comments are valid but cloud didn't exist when this was opened and everything described in the issue type is provided by the free plugin. So the length of this issue isn't relevant. I totally agree about their lack of support to important issues. I think you're harping on the wrong one.
            Hide
            martin.gregory1073735577 Martin Gregory added a comment -

            Jo Rhett do I understand this right: you have a server installation, and are using a plugin that works on a server installation only?

            And on that basis you are declaring that this issue is unimportant?

            Screw you cloud users, eh?

            Show
            martin.gregory1073735577 Martin Gregory added a comment - Jo Rhett do I understand this right: you have a server installation, and are using a plugin that works on a server installation only? And on that basis you are declaring that this issue is unimportant? Screw you cloud users, eh?
            Hide
            olivier.croquette Olivier Croquette added a comment -

            @Jo Rhett: thanks for the link and the information. I understand that the issue might be mitigating for some JIRA user thanks to the plugin, however 3rd party plugins always have their drawbacks (long term maintenance, compatibility with other plugins, custom fields, configuration management...). We don't pay $3,300 per year to Atlassian to have to deal with that. Especially considering that there are 20 similar issues we need a solution for. Look at these issues and you will realize how much time is wasted by Atlassian customers trying to find workarounds through configuration tweaks, self-made scripts or 3rd party plugin. It shows clearly how Atlassian is failing to support their existing customers.

            @Patrick Wolf: Considering that 1) Atlassian is doing pretty well, 2) is targeting new markets with their current product lines, and 3) some antediluvian requests are really basic (like this one, or JRA-1369, JRA-22640, JRA-34423, JRA-24907), the answer to your question is clear: Atlassian clearly doesn't care about their existing customers.

            Show
            olivier.croquette Olivier Croquette added a comment - @Jo Rhett: thanks for the link and the information. I understand that the issue might be mitigating for some JIRA user thanks to the plugin, however 3rd party plugins always have their drawbacks (long term maintenance, compatibility with other plugins, custom fields, configuration management...). We don't pay $3,300 per year to Atlassian to have to deal with that. Especially considering that there are 20 similar issues we need a solution for. Look at these issues and you will realize how much time is wasted by Atlassian customers trying to find workarounds through configuration tweaks, self-made scripts or 3rd party plugin. It shows clearly how Atlassian is failing to support their existing customers. @Patrick Wolf: Considering that 1) Atlassian is doing pretty well, 2) is targeting new markets with their current product lines, and 3) some antediluvian requests are really basic (like this one, or JRA-1369 , JRA-22640 , JRA-34423 , JRA-24907 ), the answer to your question is clear: Atlassian clearly doesn't care about their existing customers.
            Hide
            jkimbrell724283205 Julie Hill Kimbrell added a comment -

            re: "Another alternative is to use "@mentions" in the description of an issue to notify end users about the issue being created, and the recipients can then decide if they want to watch the issue" >> Dave Meyer, your suggestion of @mentions in issue description during creation is not sending a notification to the mentioned person. Please let us know if this functionality will be fixed/available in the near future.

            Show
            jkimbrell724283205 Julie Hill Kimbrell added a comment - re: "Another alternative is to use "@mentions" in the description of an issue to notify end users about the issue being created, and the recipients can then decide if they want to watch the issue" >> Dave Meyer, your suggestion of @mentions in issue description during creation is not sending a notification to the mentioned person. Please let us know if this functionality will be fixed/available in the near future.

              People

              • Assignee:
                Unassigned
                Reporter:
                mick Mick Hollins
              • Votes:
                602 Vote for this issue
                Watchers:
                321 Start watching this issue

                Dates

                • Created:
                  Updated: