How to create an issue on another project as part of transition

Hello All,


We have been using the "Adaptivist ScriptRunner"s "clone an issue and links" function in our transition to clone tickets to another project.  

I now need to "create" an issue on another project as part of the transition, without cloning it. Preferably, I'd like to see a "screen" that is similar to regular "issue creation screen" when agents press the transition button. 

It sounds really easy but I haven't been able to find a solution yet. I wonder if I can modify "clones an issue and links" to achieve the same task but I'm open to any/all suggestions.

 

Thanks,

1 answer

I have a request please. Could you please share your Clone and Issue Links Senarios as well as something about Adaptivist ScriptRunner?

I beleive what you have done will help me.  Below is my condition:

I have two Projects i.e. Project A and Project B. I need to create a bug from A and assign that bug to the Project B since the issue is releated to Project B or the bug of Project A should be created in Project B when a ceratain field such as COMPONENT field contain a value related to project B.

 I do not have access to project B So I cannot open directly in project B. Once a bug is created that bug is reported in Project A and should be Reported in project B too. 

I could have created a bug in Project A and in the Assignee field I could mention the ServiceID of Project B by which Users of Project B get email notification but doig so would not create a bug in Project B. User in project B will only get email notification.

Please advice.

 

Hey sorry for the late response, basically I'm using adaptivist scriptrunner's "Clones an issue and links" function. I don't know the mechanics behind the script but that's the condition I use: 

 

import com.atlassian.jira.component.ComponentAccessor
import com.atlassian.jira.issue.link.IssueLinkManager

def issueLinkManager = ComponentAccessor.getComponent(IssueLinkManager)

! issueLinkManager.getInwardLinks(issue.getId()).any {
it.issueLinkType.name == "Blocks"
}

 

Also, these are the additional issue actions 

 

import com.atlassian.jira.component.ComponentAccessor
import com.atlassian.jira.issue.Issue


def currentAppUser = ComponentAccessor.getJiraAuthenticationContext().getLoggedInUser()


issue.setReporter(currentAppUser);

 

What it does is, it takes an issue, clones every single common field in two projects, links the new ticket to the original ticket with "blocks" relationship type. 

 

Also, the additional action simply clears the assignee as the new ticket needs to be triaged from ground up as a complete new ticket. 

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,312 views 14 20
Join discussion

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
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot