Set focus on a cloned issue


I'm using script runner to clone an issue during trantision, the probelm is that there is no notification when that issue is created.

Is there a way to automatically switch to the new issue ? or at least get that little notification box syaing that an issue is created with a link to that issue?

2 answers


This is not possible by default. I think its correct that the old issue is shown with new status as that was the intention of the user. In background whatever needs to be done is done, like clone of issue. User gets a link to the cloned issue anyways in the current issue as linked task.


Jira default behaviour is to set focuse on the newly cloned issue.

Is there a way get this default behaviour with script runner?

or .. is there a way to notify the user " your cloned issue is .... " ?

Yes JIRA default behaviour is based on user intention to clone the issue. So that is correctly implemented to open the cloned issue.

Notification is not by the way of pop-up/message box. But it is a link to the current issue "Cloned".

I dont think without custom implementation, you can achieve what you want.

Oded - if you can use 3.0-beta you can use this method in the additional actions:

Thanks Jamie.. I will check it out..

Hi jamie,

After upgrading to 3.0, We started getting this error in the catalina.log file :

/secure/QuickCreateIssue.jspa [scriptrunner.jira.workflow.ScriptWorkflowFunction] Script function failed on issue: IC-22994, actionId: 1, file: null

groovy.util.ResourceException: Malformed URL: bundle://147.0:0/, null

any idea why?

Hi there... can you check the workflow functions you have on the create transition? Somehow the file path is null or it's inaccessible...?


MY scripts are under /home/jira/scripts together with some private plugins, to specify this place I added the following lines to file in jira installation.





My catalina is as follows : ( taken from the startup details )

CATALINA_BASE: /usr/local/atlassian/jira

Using CLASSPATH: /home/jira/scripts:/usr/local/atlassian/jira/bin/bootstrap.jar:/usr/local/atlassian/jira/bin/tomcat-juli.jar

I saw the 'breaking changes' wrriten in the 'Upgrading to 3.0' document but when I added "-Dplugin.script.roots=/home/jira/scripts" to the startup, My script are still not get "picked" by the script runner.

Can you please advice?

How is the script file path displayed in the UI, for the script in the particular workflow action?


Is this a plain script or is it using the CannedScript interface? If it is, can you send it to me, <firstname>.<lastname>

It is a cannedScript ..

I sent it to you.

Thanks a lot !

Hi Jamie,

The message is working great .. is there a way to add a link ( or just the issue key ) to the newly cloned issue in the message?

I think the issue key of the newly cloned issue is available as issue.key, no?

Thanks Jamie, issue.key returns a null value .. Any other suggestions ?

Sorry - is this a continuation of an old question? When you say "The message is working great" are you talking about the green popup thing after the workflow function runs?

Yes .. "the green popup thing after the workflow function runs" but when I'm using issue.key I get a null on the message ..

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Wednesday in Marketplace Apps

Marketplace Spotlight: Marketing apps for Confluence to keep your teams working on the same page


125 views 0 3
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you