• Icon: Suggestion Suggestion
    • Resolution: Fixed
    • 6.0
    • None
    • None
    • 6
    • 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.

      Update: Great news for everyone watching this issue and especially for those that that voted on the ability to Bulk Watch a list of issues... we are resolving this as FIXED!

      Two of our awesome JIRA Engineers took this request on in a ShipIt! project and we now bring it to you as part of the exciting JIRA 6.0 release (coming soon).

      Atlassian Status as of 15 November 2012

      Hi everyone,

      Thanks so much for your votes and comments on this issue.

      While we don't have plans to address this feature in the next 12 months, we are keeping this on our roadmap and plan to address it in the future, along with other bulk actions like JRA-13245.

      In the meantime, there are a number of possible solutions, including a plugin on the Atlassian Marketplace and several scripts offered by other customers in the comments below. Since these solutions are not available in JIRA OnDemand, we are keeping this in our roadmap and want to make sure all customers have access to a solution.

      While we will not be addressing this feature request in the next 12 months, we plan to resolve several other top voted feature requests in the next 12 months, including JRA-3821, JRA-1549, JRA-5783, and JRA-7659. And we have recently resolved both JRA-19083 and JRA-7686, two other highly voted feature requests.

      Thanks for your patience and we hope you appreciate our open approach to feature requests.

      Cheers,

      Bryan
      JIRA Product Management
      brollins at atlassian dot com

        1. 2009-05-13 09:21.bmml
          0.0 kB
        2. 2009-05-13 09:21.bmml
          0.4 kB
        3. 2009-05-13 09:21.png
          2009-05-13 09:21.png
          0.1 kB

            [JRASERVER-2429] Bulk Watch

            Hi gary.mellor,

            Indeed, that looks like a bug. As suggested by luke1410, could you please raise this with us at https://support.atlassian.com so a support engineer can confirm this and raise a proper bug report with the engineering team?

            Thanks in advance

            Regards,

            Oswaldo Hernández.
            JIRA Bugmaster.
            [Atlassian].

            Oswaldo Hernandez (Inactive) added a comment - Hi gary.mellor , Indeed, that looks like a bug. As suggested by luke1410 , could you please raise this with us at https://support.atlassian.com so a support engineer can confirm this and raise a proper bug report with the engineering team? Thanks in advance Regards, Oswaldo Hernández. JIRA Bugmaster. [Atlassian] .

            @Gary: In cases like these it's normally more helpful to contact the support via support.atlassian.com or create a new JIRA issue, if you are certain there's a bug in this implementation (linking it to this one).

            Stefan Hett added a comment - @Gary: In cases like these it's normally more helpful to contact the support via support.atlassian.com or create a new JIRA issue, if you are certain there's a bug in this implementation (linking it to this one).

            This doesn't work if I want to bulk remove myself as a watcher from a bunch of closed tickets or a single closed ticket (yes, I have specific reason to do this). Ordinarily JIRA advises if you're trying to do something to a closed issue and tell you that you can't do it (you have to re-open the issue(s), make the change and then close them again, which is a total nightmare but one for a separate ticket) but not in this instance. I have just over 600 issues I wish to 'unwatch' that are closed. I can complete the 4 steps to the operation of the bulk change but the UI shows that the operation started and ended at the same time which immediately raised my suspicions and when I clicked the Acknowledge button I was returned to exactly the same filter view as before and nothing had changed. I went into an individual ticket and was able to 'unwatch' that but due to the same problem of the issue already being closed (I'm guessing), when you go back into that ticket you can see that you are still watching it. I'm suggesting that this is a bug in the implementation. If I am being told I am 'unwatching' an issue as either an individual ticket or a bulk change I expect that to be the case or at the very least be told why it cannot be done. The current behaviour is very confusing as it indicates the operations have been successful when in actual fact they haven't at all.

            Lisa Winkless added a comment - This doesn't work if I want to bulk remove myself as a watcher from a bunch of closed tickets or a single closed ticket (yes, I have specific reason to do this). Ordinarily JIRA advises if you're trying to do something to a closed issue and tell you that you can't do it (you have to re-open the issue(s), make the change and then close them again, which is a total nightmare but one for a separate ticket) but not in this instance. I have just over 600 issues I wish to 'unwatch' that are closed. I can complete the 4 steps to the operation of the bulk change but the UI shows that the operation started and ended at the same time which immediately raised my suspicions and when I clicked the Acknowledge button I was returned to exactly the same filter view as before and nothing had changed. I went into an individual ticket and was able to 'unwatch' that but due to the same problem of the issue already being closed (I'm guessing), when you go back into that ticket you can see that you are still watching it. I'm suggesting that this is a bug in the implementation. If I am being told I am 'unwatching' an issue as either an individual ticket or a bulk change I expect that to be the case or at the very least be told why it cannot be done. The current behaviour is very confusing as it indicates the operations have been successful when in actual fact they haven't at all.

            timineri added a comment -

            Thanks Oswaldo,

            Sorry, I must have misunderstood the issue. I need to bulk remove watchers, not bulk add myself as a watcher. For example, we just did an import from Bugzilla to JIRA and people in the bugzilla CC come over as watchers on the issue. For several reasons I now need to strip out specific watchers that either do not exist in real life... at least not any more.

            Michael

            timineri added a comment - Thanks Oswaldo, Sorry, I must have misunderstood the issue. I need to bulk remove watchers, not bulk add myself as a watcher. For example, we just did an import from Bugzilla to JIRA and people in the bugzilla CC come over as watchers on the issue. For several reasons I now need to strip out specific watchers that either do not exist in real life... at least not any more. Michael

            Hi timineri,

            You should be able to do this like any other "Bulk Operation". There should be a "new" Watch Issues operation option. If you would like more assistance please don't hesitate to get in touch with us via a support ticket at https://support.atlassian.com

            Regards,

            Oswaldo Hernández.
            JIRA Bugmaster.
            [Atlassian].

            Oswaldo Hernandez (Inactive) added a comment - Hi timineri , You should be able to do this like any other "Bulk Operation". There should be a "new" Watch Issues operation option. If you would like more assistance please don't hesitate to get in touch with us via a support ticket at https://support.atlassian.com Regards, Oswaldo Hernández. JIRA Bugmaster. [Atlassian] .

            timineri added a comment -

            Was this included in JIRA 6 as the update suggests? If so, is there information on how to use this?

            timineri added a comment - Was this included in JIRA 6 as the update suggests? If so, is there information on how to use this?

            Bardiya added a comment -

            One workaround that worked for me is to have the watcher settings set so that the user is automatically added as a watcher after commenting on the ticket.

            Once that's set, do a bulk comment action to all the tickets, I just typed 'Joining this ticket as a watcher' and I was added to the list of watchers.

            Bardiya added a comment - One workaround that worked for me is to have the watcher settings set so that the user is automatically added as a watcher after commenting on the ticket. Once that's set, do a bulk comment action to all the tickets, I just typed 'Joining this ticket as a watcher' and I was added to the list of watchers.

            Here's a scripted way to be able to unwatach any list of issues that are shown in a search result: https://github.com/rubyboy/jira-bulk-unwatch
            This could also be applied similarly to watching issues (change the "DELETE" method in the script to "PUT")

            Ruby Boyarski added a comment - Here's a scripted way to be able to unwatach any list of issues that are shown in a search result: https://github.com/rubyboy/jira-bulk-unwatch This could also be applied similarly to watching issues (change the "DELETE" method in the script to "PUT")

            bede added a comment -

            this feature would also be candidate to have on the user profile page, similar to what is done in FISHEYE already

            bede added a comment - this feature would also be candidate to have on the user profile page, similar to what is done in FISHEYE already

            prenagha added a comment -

            prenagha added a comment - My workaround https://gist.github.com/3098888

              Unassigned Unassigned
              dave@atlassian.com dave (Inactive)
              Votes:
              229 Vote for this issue
              Watchers:
              144 Start watching this issue

                Created:
                Updated:
                Resolved: