nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

[Scriptrunner] Impossible to copy attachements from an issue to another with a listener

Antoine _Klee Group_

Hello,

I am using a Scriptrunner Listener in order to create several issue when an issue from a certain type is created.

I also want to copy the attachments from that trigger issue.

The code works fine when testing it in the Script Console but once I switch to building a listener (or post-function), that does not work anymore.

Here's a MWE:

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

def myAttachmentManager = ComponentAccessor.getAttachmentManager()

// The trigger issue
Issue triggerIssue = event.getIssue()

List listOfIssuesToBeCreated= []

for (value in ['1', '2']) {
Issue createdIssue = Issues.create("Some project key", "Some issue type") {
        setSummary("${triggerIssue .getSummary()} - request $value")
        setCustomFieldValue(12011, value)
        setLinks("relates to", triggerIssue.getKey() )
       // setting other fields
    }
    listOfIssuesToBeCreated.add(createdIssue.getKey())
}
for (issueKey in listOfIssuesToBeCreated) {
    log.info("Copying Attachements from ${triggerIssue.getKey()} to ${issueKey}")
Map resultOfAttachementCopy = myAttachmentManager.copyAttachments(triggerIssue, null, issueKey)
log.info(resultOfAttachementCopy)
}

The `resultOfAttachementCopy` Map is always empty.

I used the following documentation (AttachmentManager (Atlassian JIRA 9.4.17 API))

As I said, when I execute this script in a Script Console, forcing the triggerIssue to be like triggerIssue = Issues.getByKey("My issue key") that works fine.

What am I missing?

Accepted answers

Antoine _Klee Group_

Well…

The code is actually working fine.

Instead of creating a new issue each time to test my post-functions, I cloned it. Seems like it's more the "clone" feature of Jira that does not work rather than the script.

Many thanks to you @Josh_Unito @Sean Chua _Adaptavist_

All comments

Josh_Unito

Listeners run in the background, triggered by specific events. They execute under a system user or a specific user you configure. But if the user doesn't have the right permissions to view or copy attachments, you're going to have problems.

Instead of relying on the ComponentAccessor to get the AttachmentManager, you could explicitly specify the user whose permissions you want to use for the copy operation.

Replace "username_with_permissions" with the actual username of whoever has the necessary permissions.

Alternatively, if you prefer a faster, simpler solution to avoid this kind of troubleshooting, you could try syncing Jira instances with a no-code tool like Unito's two-way integration for Jira!

Sean Chua _Adaptavist_

Hey @Antoine _Klee Group_ ,

Have you tried using this sample script Copy an Issue to a Separate Project from our Adaptavist Library?

Minimal changes to match my instance and requirements. Created an issue in Project 1, and an issue was copied/cloned into Project 2. The CF (eg: Target Start / End, wasn't copied because the other project didn't have that CF assigned).

Project 1 issue:

Project 2 issue:

Hope that helps.

Sean

Antoine _Klee Group_

Thanks @Sean Chua _Adaptavist_, that could do the job infact.

How to edit the issue type, summary, description as well as a multi select list custom field of the cloned issue in this script though?

I would also like to use a specific link linking this cloned issue to the trigger one (the "relates to" link type)

I don't find that to be explicite in the code snipped you shared.

Best

Antoine _Klee Group_

Hi Thanks for hte reply @Josh_Unito

Replace "username_with_permissions" with the actual username of whoever has the necessary permissions.

What do you mean by that? I don't see this whether in my script or the doc I shared.

The trigger user is currently myself (I'm the reporter of the "cloned" issues) and I have the permissions to add attachements so I don't know if that's the matter.

Sean Chua _Adaptavist_

Just for understanding, do you need issues to be created simultaneously into several projects? or perhaps you are looking for like a 1 - 1 kinda thing?

Cause if it is 1-1, then actually using this Built-in Script Listener should meet your needs to clone and link directly. You just need to go over to "Create Listener" , click into "Issues" tab and there is an easy to use UI for you to set it up.

Then if you need further script samples, you can find our Adaptavist Library samples directly from the </>Example Scripts button.

Pasted Graphic.png

But if you do really do need the script changes itself, you will need to add some code after:

// Execute the clone action with the specified inputs
def updatedExecutionContext = newClonedIssue.execute(inputs, executionContext)
//The issue has been successfully cloned
assert updatedExecutionContext.newIssue

Hope that helps.

Sean

Antoine _Klee Group_

Thanks for your reply.

The use case is that I have the triggerIssue that holds a multiselect customfield.

For each of the selected values (what is described in the MWE as

for (value in ['1', '2']) {

), I want to create an issue of another issue type, linked to that trigger issue, that is basically a clone, with all fields copied from the trigger issue, within the same project. I just want to adjust the summary, description, and that multi-select list to only hold a single value in the clone and not all from the trigger issue.

I tried using a post-function in the workflow instead of the listener and the attachments aren't copied either btw...

My original script works fine for all fields except the attachements. Since it seems to be super close to the desired behaviour, I'm wondering if I'm missing something simple. Especially considering it does work in the script console.

Josh_Unito

Oops! Sorry I forgot to paste the code I had in mind. That comment was in this context:

import com.atlassian.jira.component.ComponentAccessor
import com.atlassian.jira.issue.AttachmentManager
import com.atlassian.jira.issue.Issue
import com.atlassian.jira.user.ApplicationUser

ApplicationUser copyUser = ComponentAccessor.getUserManager().getUserByKey("username_with_permissions") 
def myAttachmentManager = ComponentAccessor.getComponent(AttachmentManager)

Issue triggerIssue = event.getIssue()

List<String> listOfIssuesToBeCreated = []

for (value in ['1', '2']) {
Issue createdIssue = Issues.create("Some project key", "Some issue type") {
setSummary("${triggerIssue.getSummary()} - request $value")
setCustomFieldValue(12011, value)
setLinks("relates to", triggerIssue.getKey())
// setting other fields
}
listOfIssuesToBeCreated.add(createdIssue.getKey().toString())

sleep(1000) // Add a delay for indexing
}

for (String issueKey in listOfIssuesToBeCreated) {
log.info("Copying Attachments from ${triggerIssue.getKey()} to ${issueKey}")
Map result = myAttachmentManager.copyAttachments(triggerIssue, copyUser, issueKey)
log.info(result)
}

But it sounds like you already have an answer above! Sorry about the mixup.

Antoine _Klee Group_

Thanks @Josh_Unito, well I tried specifiying the user and sleep time and still have the same behaviour. Attachements aren't copied

Also tried running those codes in post-functions, and splitting them in two : one post-function on the "trigger Issue's workflow", the other on the "issues to be created" workflow, after the "indexing issues in the database" default post-function. And it still won't work...

Seems like the issue is with the copyAttachments but I can't figure out why.

Antoine _Klee Group_

Well…

The code is actually working fine.

Instead of creating a new issue each time to test my post-functions, I cloned it. Seems like it's more the "clone" feature of Jira that does not work rather than the script.

Many thanks to you @Josh_Unito @Sean Chua _Adaptavist_

Josh_Unito

Glad to hear it worked out!

I think they have the right idea. Once we start cloning, when does it stop? First Dolly the Sheep, now Jira issues, then one day it'll be human beings!

Sean Chua _Adaptavist_

Apologies I couldn't help more effectively as I'm based out of Malaysia (+8 UTC), so our hours didn't align, nevertheless, Good to hear you've got it working!

Please don't hesitate to create a Support Ticket with us in the future. We are always happy to help where possible!

Have a great one ahead

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

scriptrunner

jira

listener

script-listener

jira-data-center

data-center

hapi