• 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

            Hi, a new plugin has come to rescue those waiting for this issue. Checkout Bug Watcher at https://marketplace.atlassian.com/plugins/com.metainf.jira.plugin.bug-watcher. Project watch, bulk watch, personal notification scheme are all available. Filter watch is coming soon.

            Tibor Hegyi [META-INF] added a comment - Hi, a new plugin has come to rescue those waiting for this issue. Checkout Bug Watcher at https://marketplace.atlassian.com/plugins/com.metainf.jira.plugin.bug-watcher . Project watch, bulk watch, personal notification scheme are all available. Filter watch is coming soon.

            I just imported a project and need to refactor its assignments including watchers... being able to bulk-change watchers is really lacking here.

            Richard Eckart de Castilho added a comment - I just imported a project and need to refactor its assignments including watchers... being able to bulk-change watchers is really lacking here.

            Paul Fox added a comment -

            Ironically, I'm turning off my watch of this issue today as I'm tired of getting emails about it....

            Paul Fox added a comment - Ironically, I'm turning off my watch of this issue today as I'm tired of getting emails about it....

            Votes =148+1.

            srujan reddy added a comment - Votes =148+1.

            Ryan Connolly added a comment - - edited

            Fwiw: I've created a user script that I use since this is still an open request.
            It does bulk watch and unwatch in issue navigator edit view but not (yet) unwatch: http://userscripts.org/scripts/show/124685

            Ryan Connolly added a comment - - edited Fwiw: I've created a user script that I use since this is still an open request. It does bulk watch and unwatch in issue navigator edit view but not (yet) unwatch : http://userscripts.org/scripts/show/124685

            We would like this feature too!

            Bulk watch/unwatch and group add(individually removable) would be nice.

            Masahiro Iwao added a comment - We would like this feature too! Bulk watch/unwatch and group add(individually removable) would be nice.

            it would be nice to be able to set a group as a watchers in the workflow post function, this way they could unwatch if they need to.

            Becket Hackett added a comment - it would be nice to be able to set a group as a watchers in the workflow post function, this way they could unwatch if they need to.

            We want to do a bulk unwatch.Please enable this feature.

            Honeywell JIRA Admin added a comment - We want to do a bulk unwatch.Please enable this feature.

            I'd like to be able to bulk unwatch as well. As a manager I watch a lot of items and would like to keep the top 15 watched items on my dashboard. But with so many items watched I don't see the ones I want to see. I have over 2500 watched items now and I'd like to unwatch all the items that are closed/resolved.

            Shawn Smith added a comment - I'd like to be able to bulk unwatch as well. As a manager I watch a lot of items and would like to keep the top 15 watched items on my dashboard. But with so many items watched I don't see the ones I want to see. I have over 2500 watched items now and I'd like to unwatch all the items that are closed/resolved.

            jkuner added a comment -

            Agreed - I would love the ability at least to add watchers within the Bulk Operations tool.

            jkuner added a comment - Agreed - I would love the ability at least to add watchers within the Bulk Operations tool.

            Philipp added a comment - - edited

            I would also appreciate the possibility to bulk watch and bulk unwatch jira issues because that would save a lot of time and I think this feature is as important as bulk editing or moving issues.

            Philipp added a comment - - edited I would also appreciate the possibility to bulk watch and bulk unwatch jira issues because that would save a lot of time and I think this feature is as important as bulk editing or moving issues.

            Anna Berns added a comment -

            While it would be really great to have in the web interface as well, I found that you can use the Jira Client to add yourself as a watcher to a group of Jira's at once

            Anna Berns added a comment - While it would be really great to have in the web interface as well, I found that you can use the Jira Client to add yourself as a watcher to a group of Jira's at once

            Alex Chew added a comment -

            I'd like to get this feature ASAP. This feature can help me a lot

            Alex Chew added a comment - I'd like to get this feature ASAP. This feature can help me a lot

            please give us this feature

            Ludger Breitbach added a comment - please give us this feature

            We would like to get this feature too

            Wolfgang Fellner added a comment - We would like to get this feature too

            Ian Daniel added a comment -

            I'm not at Atlassian anymore, but I'm still an enthusiastic JIRA user and evangelist in my new job, and I still really want to be able to do a bulk unwatch.

            Cheers,
            Ian

            Ian Daniel added a comment - I'm not at Atlassian anymore, but I'm still an enthusiastic JIRA user and evangelist in my new job, and I still really want to be able to do a bulk unwatch. Cheers, Ian

            DITTO TO Ian Daniel [Atlassian]
            "I'd love to be able to do a Bulk Unwatch. I often have to clean up my watched issues list, as I watch a fair list of support issues for other engineers that I want to monitor for a while. The only way I can clean up my watch list is by running the predefined Watched Issues issue filter (via the Watched Issues portlet), then one by one clicking on the Unwatch link next to each of them. I can't do a bulk edit on this predefined filter, I can't create my own filter that returns my watched issues, and in any case bulk edit doesn't allow me to unwatch an issue."

            Josephine L Cheatham added a comment - DITTO TO Ian Daniel [Atlassian] "I'd love to be able to do a Bulk Unwatch. I often have to clean up my watched issues list, as I watch a fair list of support issues for other engineers that I want to monitor for a while. The only way I can clean up my watch list is by running the predefined Watched Issues issue filter (via the Watched Issues portlet), then one by one clicking on the Unwatch link next to each of them. I can't do a bulk edit on this predefined filter, I can't create my own filter that returns my watched issues, and in any case bulk edit doesn't allow me to unwatch an issue."

            Added UI Mockup: <2009-05-13 09:21>

            Werner Huber added a comment - Added UI Mockup: <2009-05-13 09:21>

            aberdeen61 added a comment -

            Bulk unwatch is a concern. We migrated from Bugzilla where the issues that were cc'ed for a user were created as watches. In Bugzilla there were separate options for controlling the cc emails and a bulk method to remove the many cc adds. I'm just trying to undo the impact of the migration so I can use Jira in its expected form. Having hundreds or thousands of watches prevents me from getting at the small number I still want to watch.
            Unwatching an issue seems to put a heavy strain on the server so even clicking unwatch for all the issues on a single page can have a serious performance impact on the jira server.

            aberdeen61 added a comment - Bulk unwatch is a concern. We migrated from Bugzilla where the issues that were cc'ed for a user were created as watches. In Bugzilla there were separate options for controlling the cc emails and a bulk method to remove the many cc adds. I'm just trying to undo the impact of the migration so I can use Jira in its expected form. Having hundreds or thousands of watches prevents me from getting at the small number I still want to watch. Unwatching an issue seems to put a heavy strain on the server so even clicking unwatch for all the issues on a single page can have a serious performance impact on the jira server.

            Would be great to watch a entire version.
            I don't think everybody can use the work around given above, so atleast watching multiple issues of a version should be possible

            Ajay Godbole added a comment - Would be great to watch a entire version. I don't think everybody can use the work around given above, so atleast watching multiple issues of a version should be possible

            Chad Loder added a comment -

            The Filter Subscription workaround does not actually help me as a manager because the subscription email does not contain the issue status and the email also doesn't show me "what changed" since the last email. A Bulk Watch would really really help.

            Chad Loder added a comment - The Filter Subscription workaround does not actually help me as a manager because the subscription email does not contain the issue status and the email also doesn't show me "what changed" since the last email. A Bulk Watch would really really help.

            Salutations,

            This is a good added feature in JIRA. Having a page/screen that lets you check/select issues you want to watch, something that looks like the Bulk Edit Operation screen, instead of going to every issues and opening it one by one then click the "Watch it" link.

            Thanks and God bless.

            Richmond-rae G. Dalisay added a comment - Salutations, This is a good added feature in JIRA. Having a page/screen that lets you check/select issues you want to watch, something that looks like the Bulk Edit Operation screen, instead of going to every issues and opening it one by one then click the "Watch it" link. Thanks and God bless.

            Neal –

            That's an 'easy workaround' only if you have a JIRA install that has not had a proliferation of notification schemes. Since the schemes don't inherit, my users are now all asking for various group custom field watchers. And they're mighty confused when the link to see who's watching an issue doesn' show who's actually watching the issue.

            Best Practical's RT3.X does a much better job of this.

            Peter Burkholder added a comment - Neal – That's an 'easy workaround' only if you have a JIRA install that has not had a proliferation of notification schemes. Since the schemes don't inherit, my users are now all asking for various group custom field watchers. And they're mighty confused when the link to see who's watching an issue doesn' show who's actually watching the issue. Best Practical's RT3.X does a much better job of this.

            Jason, here's a very easy workaround.

            Create a group called "Project A Watchers". Set up the notification scheme of that project to include group "Project A Watchers" wherever it currently has "All Wtachers".

            Now, all you need is to be able to easily add to /remove people from this group.

            If you're OK with asking an admin to do it, then you're set.

            I am still on 3.6 so I don't use roles and I use an Assignable Admin plugin.So, if you're OK with members of this group also being an assignable user, you could add this group to the assignable users and then ay project admin can edit that group's members. Maybe in later versions there is a better way of editing a group.

            Neal Applebaum added a comment - Jason, here's a very easy workaround. Create a group called "Project A Watchers". Set up the notification scheme of that project to include group "Project A Watchers" wherever it currently has "All Wtachers". Now, all you need is to be able to easily add to /remove people from this group. If you're OK with asking an admin to do it, then you're set. I am still on 3.6 so I don't use roles and I use an Assignable Admin plugin.So, if you're OK with members of this group also being an assignable user, you could add this group to the assignable users and then ay project admin can edit that group's members. Maybe in later versions there is a better way of editing a group.

            This is by far my biggest complaint about Jira. If you are a product manager and need to watch over certain parts of an iteration it is extremely painful to do it. Where does this sit on the product roadmap?

            Jason Schwartz added a comment - This is by far my biggest complaint about Jira. If you are a product manager and need to watch over certain parts of an iteration it is extremely painful to do it. Where does this sit on the product roadmap?

            I'd love to be able to do a Bulk Unwatch. I often have to clean up my watched issues list, as I watch a fair list of support issues for other engineers that I want to monitor for a while. The only way I can clean up my watch list is by running the predefined Watched Issues issue filter (via the Watched Issues portlet), then one by one clicking on the Unwatch link next to each of them. I can't do a bulk edit on this predefined filter, I can't create my own filter that returns my watched issues, and in any case bulk edit doesn't allow me to unwatch an issue.

            Ian Daniel [Atlassian] added a comment - I'd love to be able to do a Bulk Unwatch. I often have to clean up my watched issues list, as I watch a fair list of support issues for other engineers that I want to monitor for a while. The only way I can clean up my watch list is by running the predefined Watched Issues issue filter (via the Watched Issues portlet), then one by one clicking on the Unwatch link next to each of them. I can't do a bulk edit on this predefined filter, I can't create my own filter that returns my watched issues, and in any case bulk edit doesn't allow me to unwatch an issue.

            Thanks. Not perfect, but this helps for now.

            Christopher Pickslay added a comment - Thanks. Not perfect, but this helps for now.

            AntonA added a comment -

            Christopher,

            JIRA allows to have a subscription to a search request:
            http://www.atlassian.com/software/jira/docs/latest/issue_filters_subscribing.html

            If you create a filter that finds relevant issues and also restrict it to issues that have only been updated in the last, say 24 hours.

            This might not give you 100% of what you are after, but get you some of the way there.

            Cheers,
            Anton

            AntonA added a comment - Christopher, JIRA allows to have a subscription to a search request: http://www.atlassian.com/software/jira/docs/latest/issue_filters_subscribing.html If you create a filter that finds relevant issues and also restrict it to issues that have only been updated in the last, say 24 hours. This might not give you 100% of what you are after, but get you some of the way there. Cheers, Anton

            It struck me that an alternative approach that would work for us is if we
            could create a Notification Scheme that only applies to issues that match a
            filter. In some ways, that would be preferable, as it would serve the same
            purpose but be more flexible.

            Christopher Pickslay added a comment - It struck me that an alternative approach that would work for us is if we could create a Notification Scheme that only applies to issues that match a filter. In some ways, that would be preferable, as it would serve the same purpose but be more flexible.

            I'd really like this feature. We work in 2-week iterations, logging multiple issues per iteration. Each of those issues requires one or more watchers, which we currently have to set up individually.

            Christopher Pickslay added a comment - I'd really like this feature. We work in 2-week iterations, logging multiple issues per iteration. Each of those issues requires one or more watchers, which we currently have to set up individually.

            AntonA added a comment -

            Abhishek,

            At the moment the feature is not available. Due to the large number of feature requests, unfortunately, we do not have an implementation date for this feature.

            Cheers,
            Anton

            AntonA added a comment - Abhishek, At the moment the feature is not available. Due to the large number of feature requests, unfortunately, we do not have an implementation date for this feature. Cheers, Anton

            Hi Team,

            There are many user asking for bulk editing watcher list.
            Could you please tell us, this feature is now available or not?

            Thanks,

            Abhishek Tripathi added a comment - Hi Team, There are many user asking for bulk editing watcher list. Could you please tell us, this feature is now available or not? Thanks,

            Guys, this has been open since feb '03, is this feature not soon to be implemented?

            Freyr Olafsson added a comment - Guys, this has been open since feb '03, is this feature not soon to be implemented?

            Tim, that's already logged as issue JRA-5383.

            Neal Applebaum added a comment - Tim, that's already logged as issue JRA-5383 .

            h added a comment -

            A really nice feature would be just to filter the issues that you are watching on status instead of a just a single 'watched' filter

            h added a comment - A really nice feature would be just to filter the issues that you are watching on status instead of a just a single 'watched' filter

            Ideally I'd love to see vote & watch statuses implemented as a per-user property on each issue. By this I mean, for them to have the same or similar functionality to other properties such as:

            • inclusion in navigator
            • search fields (at least X votes, where I am watching)
            • inclusion in bulk change
            • inclusion in portlets,etc..

            Mark Stanton added a comment - Ideally I'd love to see vote & watch statuses implemented as a per-user property on each issue. By this I mean, for them to have the same or similar functionality to other properties such as: inclusion in navigator search fields (at least X votes, where I am watching) inclusion in bulk change inclusion in portlets,etc..

            We also want to execute the add watchers option on a lot of issues by the "Bulk Changes" process.
            Would you can tell us when it will be added ?
            Is there any option (maybe true the database) to do it at the meantime ? Do you have any workaround for now ?
            Thanks

            Amdocs Company added a comment - We also want to execute the add watchers option on a lot of issues by the "Bulk Changes" process. Would you can tell us when it will be added ? Is there any option (maybe true the database) to do it at the meantime ? Do you have any workaround for now ? Thanks

            My users are requesting ability to make bulk update of their watches.

            Olle Friman added a comment - My users are requesting ability to make bulk update of their watches.

            This would be a nice feature, there are times when I want to watch all issues in a certain release or all critical issues. This feature would allow me to search for a set of issue and say 'Watch All' or 'Unwatch All', that would be very handy.

            Bernard Durfee added a comment - This would be a nice feature, there are times when I want to watch all issues in a certain release or all critical issues. This feature would allow me to search for a set of issue and say 'Watch All' or 'Unwatch All', that would be very handy.

            <reminder>
            I now have a use case for this. I would like to show our external client as the reporter, so it would be handy to generate a filter of those issues and tag the ones I want to watch
            </reminder>

            Neal Applebaum added a comment - <reminder> I now have a use case for this. I would like to show our external client as the reporter, so it would be handy to generate a filter of those issues and tag the ones I want to watch </reminder>

            angel added a comment -

            With an option to bulk unwatch. Could be extented to votes too.

            Cheers
            Aggelos P.

            angel added a comment - With an option to bulk unwatch . Could be extented to votes too. Cheers Aggelos P.

            MarkC added a comment -

            Jeff,

            To be honest, we haven't looked into implementing this feature yet, so I'm pretty sure this one won't be donw by 3.1 (Feb 2005).

            Hope that doesn't cause too much pain.

            Cheers

            Mark C

            MarkC added a comment - Jeff, To be honest, we haven't looked into implementing this feature yet, so I'm pretty sure this one won't be donw by 3.1 (Feb 2005). Hope that doesn't cause too much pain. Cheers Mark C

            how's this one looking for the February 3.1 timeframe?

            Jeff Barrett added a comment - how's this one looking for the February 3.1 timeframe?

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

                Created:
                Updated:
                Resolved: