Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-43158

Workflow Post Function to Add or Remove Watcher

XMLWordPrintable

    • 5
    • 16
    • 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.

      Current Behaviour

      • Currently there is no functionality to perform watcher management actions on transitions.

      Feature Request

      • Provide Workflow Post Function to Add or Remove a Watcher

            [JRASERVER-43158] Workflow Post Function to Add or Remove Watcher

            Emil Khairov added a comment -

            This would be a lifesaver

            Emil Khairov added a comment - This would be a lifesaver

            Benjamin Leidner added a comment -

            Senior execs have to approve a workflow at one point.  Then, they don't want to be bothered with issue updates.  I have workarounds but would love to be able to just remove them after they do their part.

            Benjamin Leidner added a comment - Senior execs have to approve a workflow at one point.  Then, they don't want to be bothered with issue updates.  I have workarounds but would love to be able to just remove them after they do their part.

            Kyle Centrella added a comment -

            ++

            Kyle Centrella added a comment - ++

            Ariana R. added a comment -

            +1

            Ariana R. added a comment - +1

            Ryan Smith added a comment -

            +1

            Ryan Smith added a comment - +1

            Antonio Dionisio added a comment -

            Hi! I am the lead developer for this free app for Server that includes this postfunction: https://marketplace.atlassian.com/apps/1220505/workflow-magic-box?hosting=server&tab=overview

            Feel free to contact us if you need support.

            Antonio Dionisio added a comment - Hi! I am the lead developer for this free app for Server that includes this postfunction:  https://marketplace.atlassian.com/apps/1220505/workflow-magic-box?hosting=server&tab=overview Feel free to contact us if you need support.

            Jason Ferris added a comment -

            When specific group of people (non customers) add an incident automatically add specific watchers. Currently I don't know how to accomplish this based off of the automation rules as they are fairly generic. 

            Jason Ferris added a comment - When specific group of people (non customers) add an incident automatically add specific watchers. Currently I don't know how to accomplish this based off of the automation rules as they are fairly generic. 

            Alexey Grevtsev added a comment -

            Use case: Add or remove different user groups as watchers to different issue types. Or even different different teams will watch issue in different statuses.

            Thanks.

            Alexey Grevtsev added a comment - Use case: Add or remove different user groups as watchers to different issue types. Or even different different teams will watch issue in different statuses. Thanks.

            Dianne M Fry-Bolton added a comment -

            Use Case: 'Services Impacted' (may be several) are entered into a Label field. The Product Management team for each 'Service' would like to added as a Watcher.

            Dianne M Fry-Bolton added a comment - Use Case: 'Services Impacted' (may be several) are entered into a Label field. The Product Management team for each 'Service' would like to added as a Watcher.

            Mark Gancsos added a comment -

            Basically the same as Cameron's use case above...

            I require this functionality for the following use case:

            • An issue is created by User X
            • User X is now done with the issue, and User Y manages it through closure
            • User X is no longer interested in this issue anymore, and currently must manually unwatch or get tons of emails

            Mark Gancsos added a comment - Basically the same as Cameron's use case above... I require this functionality for the following use case: An issue is created by User X User X is now done with the issue, and User Y manages it through closure User X is no longer interested in this issue anymore, and currently must manually unwatch or get tons of emails

              Unassigned Unassigned
              jalor Janice Alor (Inactive)
              Votes:
              195 Vote for this issue
              Watchers:
              79 Start watching this issue

                Created:
                Updated: