How do I automatically add a user as a watcher for an issue-type when a ticket is created?

[Mario Garces]

I want a particular user to be automatically added as a watcher for a specific issue-type when a ticket is created in that project.  I am using the Cloud version of JIRA.

[Rilwan Ahmed · Accepted solution]

Hi @Mario Garces / @fulya 

We can now add a particular user to watchers list  for a specific issue-type in a project. Please follow below steps to do it.

• Go to Project settings --> Automation --> Create new
• Select below details 
  •  When: Issue created
  • New condition: JQL Condition (add the required JQL. Example: Issue type = "Service Request")
  • New Action: select Manage Watchers
    under "Add these watchers", add the required user. 
  • Save

This will look like the attached image

[fulya]

Thanks for the reply, though I cannot quite figure how to work with JQL... Is it possible to create the rule without a condition since I do want this rule to apply for the whole board whatsoever.

[Rilwan Ahmed]

Hi @fulya

JQL is for filtering out tickets. You can even continue with When(issue created) and Then (New action -->Add watchers) only.

Automation rule will run for all tickets created in the project irrespective of the issue/ticket types

Please accept answer if it solves your query. 

[fulya]

[fulya]

Hi again, you could kindly see my screen above. Therefore, it seems like that I don't have the aforementioned action here.  

[Rilwan Ahmed]

Hi @fulya 

Try searching with "Manage Watcher" or just "watcher" in components section.
Instead of search, you can just scroll down to check what all options are present. 

[fulya]

I cannot believe that I gave you this much trouble for such an easy application... Thanks for your time and effort you spent explaining to me! 

[Rilwan Ahmed]

Hi @fulya ,
Please accept the answer if it has helped you find the solution. 

[fulya]

Sorry, I am not the owner of this question. Therefore I guess I am not the one to accept as an answer. Though I gave a vote to your answer, is this sufficient for you?

[Rilwan Ahmed]

Thank you. 

[Vinay Shekar S]

This can be achieved by adding custom script postfunction on "Create Issue" workflow transition.

Follow below steps:

1. Add a Post function

2. Select "Script Post-Function [ScriptRunner]"

3. Select "Custom script post-function"

4. Add below code

========================================

import com.atlassian.jira.component.ComponentAccessor;
import com.atlassian.jira.issue.MutableIssue

def userName = "username" // name of the user
def userManager = ComponentAccessor.getUserManager()
MutableIssue issue = issue as MutableIssue
def user = userManager.getUserByName(userName)

def watcherManager = ComponentAccessor.getWatcherManager()

watcherManager.startWatching(user, issue)

=========================================

5. Don't forget to move this postfunction below "Creates the issue originally"

Prerequisites: ScriptRunner app from Atlassian MarketPlace

[Maria Redlin]

Hi Vinay,

I have done so, but I get an error message on line 7 . Variable "Issue" makes a binding variable of the same name.

Please advice

Maria

[Firas Amer]

now it is possible to set it up very easily with Jira automation

[fulya]

Hello Judit, could you kindly take us through the steps? I, somehow, cannot seem to find the "Add watchers" action within Automation tab.

[Rambabu Patina _Appfire_]

Using  Update On Transition add-on you can set up a post function to automatically add watcher. For similar examples see https://bobswift.atlassian.net/wiki/spaces/CW/pages/55050519/How+to+update+issues+after+initial+issue+create

[Deleted user]

Thanks @Rambabu Patina _Appfire_ 

I have learnt something new today. :)

[Mario Garces]

@Rambabu Patina _Appfire_

Thank you, however not available for Cloud version

[Deleted user]

Hi @Mario Garces,

You may need to investigate the Script Runner plugin and build a custom script to do this, as a similar question was created with regards to your request.

There is also a feature request on Atlassian's JIRA, you may want to vote on this issue. 

Hope this helps

[Mario Garces]

@[deleted]

Thank you, the workaround given in the feature request comments worked for me.

[Corey_Tabb]

This is pretty shit service every time there is a feature that loads of people want a ticket is created people have to upvote it people upvote it and then it is never added what is the point in telling us to vote for a feature if you are never ever going to do it what feature has the public requested that you ACTUALLY ADDED i am yet to see one added that isn't oww go to this plugin and pay even tho you already pay thousands a month for us

[Steve McG]

@Corey_Tabb totally agree. Most times I look for some help on a piece of functionality with Jira the answer seems to be from someone trying to sell their add-on through the marketplace ($$$), or you have to vote for it to be added. I mean, how long do we have to wait for all the votes to be counted... It comes across as "yeah, we're not going to do that, sorry bud".

Looks like Atlassian are getting their functionality gaps filled by the marketplace and probably getting a nice little cut on the way.