• Icon: Suggestion Suggestion
    • Resolution: Won't Do
    • None
    • 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.

      Similar to CONF-22430 or JRA-33735 ,
      it would be great if we can use group when we manage watchers.

            [JRASERVER-33736] Add watchers by group

            I find it hard to believe this is not being addressed. Is there a related bug somewhere that asks the same question? Surely it makes sense to be able to add a group into the watcher field?

            Can you advise how others do it, apart from adding people one-by-one?

            Sharon Meyler added a comment - I find it hard to believe this is not being addressed. Is there a related bug somewhere that asks the same question? Surely it makes sense to be able to add a group into the watcher field? Can you advise how others do it, apart from adding people one-by-one?

            Is there any progress on this? We'd really would like to have this feature in Jira to not have to add all watchers from a department one by one.

            Alexander Yolov added a comment - Is there any progress on this? We'd really would like to have this feature in Jira to not have to add all watchers from a department one by one.

            Thanks for taking the time to raise this issue.

            Due to the large volume of JIRA feature suggestions, we have to prioritise our development efforts. In part, that means concentrating on those issues that resonate the most with our users.

            I am writing this note to advise you, that we have decided to close your Suggestion as it has not gained traction on jira.atlassian.com. We believe being upfront and direct with you will assist you in your decision making rather than believing Atlassian will eventually address this issue.

            Thank you again for your suggestion and if you have any concerns or question, please don’t hesitate to email me.

            Kind Regards,
            Kerrod Williams
            JIRA Product Management
            kerrod.williams at atlassian dot com

            Kerrod Williams (Inactive) added a comment - Thanks for taking the time to raise this issue. Due to the large volume of JIRA feature suggestions, we have to prioritise our development efforts . In part, that means concentrating on those issues that resonate the most with our users. I am writing this note to advise you, that we have decided to close your Suggestion as it has not gained traction on jira.atlassian.com. We believe being upfront and direct with you will assist you in your decision making rather than believing Atlassian will eventually address this issue. Thank you again for your suggestion and if you have any concerns or question, please don’t hesitate to email me. Kind Regards, Kerrod Williams JIRA Product Management kerrod.williams at atlassian dot com

            Tsol added a comment -

            Is a bit confusing not to have the same functionality in JIRA especially and have it in Confluence.

            In our company are used to share pages with groups in Confluence and they suppose that the same can do in JIRA.

            For that reason we have created dummy users with same name of group but this made the things even more complex because in Confluence appears a user and a group with the same name. In Confluence apart from sharing this confuses more in page restrictions.

            Tsol added a comment - Is a bit confusing not to have the same functionality in JIRA especially and have it in Confluence. In our company are used to share pages with groups in Confluence and they suppose that the same can do in JIRA. For that reason we have created dummy users with same name of group but this made the things even more complex because in Confluence appears a user and a group with the same name. In Confluence apart from sharing this confuses more in page restrictions.

              Unassigned Unassigned
              6e4387217e11 ChangJoon Lee
              Votes:
              11 Vote for this issue
              Watchers:
              18 Start watching this issue

                Created:
                Updated:
                Resolved: