Is there any possibility to override the default interface of the "Clone issue and links" post-function?
I would like to pass the project and issuetype as parameters in the "additional issue actions".
I have unpacked the script runner plugin and tried to take a peek into the code of the post-function to look for some hints, but I'm afraid I became more confused than I was before :) Not to mention the function itself seems to be scattered in three different files.
Here is an example of my desired use case:
you want something like:
issue.setIssueTypeId(3) ... etc
Ah... I think I maybe understand what you are asking. You should be able to get the selected target project key using:
static import com.onresolve.scriptrunner.canned.jira.utils.AbstractCloneIssue.FIELD_TARGET_PROJECT
Hi Jamie, I want to piggy back on this issue. Hope this is OK? I want the same scenario. Basically this: * When user moves an issue to a status. I will pop up a screen. Here he can select the project to clone this issue to from a custom field. * Once the issue is moved to this status. I want to use your clone and link post function to generate a new issue in same project with "cloned by" links. * I then want to use the "additional actions" to get the selected project and move it to the wanted project. So basically not pre-selecting the project on the post function but allowing the user to select it during transition to status. Is this doable?
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
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!
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