Issue #840 new
Scott McDonald
created an issue


Per new version of JIRA every time a users adds a ticket to the system they are automatically added as a watcher. For the parent ticket this functionality is good. However, for each individual sub-task auto created by the submitter it causes email fatigue and confusion on what sub-task is actually assigned to them. Is there a way that we can remove this functionality for sub-tasks besides turning off the system switch?

Thank you, Scott

Comments (10)

  1. Scott McDonald reporter

    Hi Fidel:

    Do I add this just once under post-function or is it needed for each ticket I am creating? For instance, under one of the workflow transitions, I'm creating up to 5 subtasks.

    Thank you, Scott

  2. Fidel Castro Armario repo owner

    Hi @Scott McDonald,

    The described post-function should be added in transition Create Issue in sub-task's workflow.

    If the same workflow is being used for normal issues and sub-tasks, then you should use the following boolean expression in parameter conditional execution:

    %{00041} != null

    where %{00041} is field code for Parent's issue key.

  3. Scott McDonald reporter

    Hi Fidel,

    I have tried every variation of that script and it's still adding the reporter as a watcher on the sub-tasks being created (on create/same workflow for parent and sub-tasks being created).

    I've used the watcher (multi-user field). I've used the watcher (watcher field) and have added/removed the conditional execution as well.

    Regards, Scott

  4. Fidel Castro Armario repo owner

    Hi @Scott McDonald,

    In your case, you should use boolean expression at conditional execution parameter, since you are sharing the same workflow for parent and sub-tasks.

    Please, attach a screenshot with post-function's tab of transition Create Issue. I want to see all the post-functions you are executing and their configurations.

  5. Fidel Castro Armario repo owner

    Hi @Scott McDonald,

    It seems that JIRA adds the reporter as watcher with some delay after issue creation, for this reason it doesn't work my solution.

    I have this alternative solution, more complex, but it works:

    1) Add "Copy a parsed text to a field" post-function to transition "Create Issue" with the following configuration:

    Captura de pantalla 2017-10-20 a las 15.03.22.png

    2) Create a reflexive transition called "Initialize Issue" in first status of the workflow (in my case Open). Reflexive transitions has the same status as origin and destination.

    3) Add condition "Transition is triggered by JIRA Workflow Toolbox post-function" to transition "Initialize Issue", so that we will be hiding the transition to human users.

    4) Add post-function "Copy a parsed text to a field" to transition "Initialize Issue" with the following configuration:

    Captura de pantalla 2017-10-20 a las 15.00.41.png

    With this solution the reporter is removed as watcher with some delay, and you will have to refresh your browser after sub-task creation in order to see that the watcher was removed.

  6. Log in to comment