How does the Code for cloning an issue in groovy look like? - usage in post-function

Hi there,

I would like to clone an issue during a post-function of a transition. As I want to clone it more than once, the pre-defined clone post-function won't do it. 

How can I access the clone functionality via groovy?

Cheers

Michaela 

1 answer

0 votes

Hi Michaela.

The code would be quite complex. I would recommend you simply use the predefined clone postfunction twice. Would that be an option?

Cheers!

Dyelamos

Hi Dyelamos,

thanks for your answer. Well I thought about this but then I need to do it not twice but more like 10 -50 times. Depending on how often I need the issue. 

Here is what I am trying to do: 

We want to have recurring tasks in Jira, all instances created at once with the appropriate due dates. Therefore I have a Master issue with all the data in it including how often the issue is repeated. On workflow transition "create instances" I create all instances at once using the post-function. Due dates are calculated and set there also. 

I currently don't see a way of calling the post-function each time of cloning an issue. 

Do you have any idea how to do it?

My current solution is to create new issues and copy the fields. Unfortunately this is also a little error prone as I need to add all needed fields by hand.

Hi Michaela. 

 

This as I explained before is quite complex. As a client of scriptrunner you have access to all of our code within the JAR. How our functions work are as follows:

1. You have a map of strings to strings with all of the paramethers.

2. You should create an instance of the function that you are using, in this case CloneIssueWithAttachments.groovy if I'm not mistaken.

3. After that, you should call the class's .doScript() function with the params map.

As I said, this might be quite challenging. Could I suggest that you contact our consultancy services to hire help on this?

Cheers!

DYelamos

Suggest an answer

Log in or Sign up to answer
Community showcase
Published 6 hours ago in Statuspage

194 years of downtime: looking back on incident data from 2018

Statuspage customers logged more than 194 years of collective incidents in 2018. That’s a whopping 87% increase from the  104 years logged in 2017 , and we aren’t even through December yet....

17 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