I've been using the JIRA CLI tool (great kit by the way). I followed examples to download an attachment list of all issues from a search query like so:
./jira.sh --action runFromIssueList --filter FOO-test --common "--action getAttachmentList --outputFormat 2 --issue @issue@ --file list.csv --append"
./jira.sh --action runFromAttachmentList --issue "FOO-1036" --common "-a getAttachment --file \"target/output/jiraclirunner/@attachment@\" --name @attachmentId@ --issue FOO-1036"
You are doing good by breaking it down into working pieces. Now, you just need to combine them all and be careful with the quoting/escaping.
--action runFromIssueList --filter FOO-test --common "--action runFromAttachmentList --issue @issue@ --common \"--action getAttachment --issue @issue@ --file \"\"target/@attachment@\"\" \" "
I am running into something interesting. If I run this:
./jira.sh --continue --verbose --action runFromIssueList --filter FOO-test --common "--action runFromAttachmentList --issue @issue@ --common \"--action getAttachment --issue @issue@ --file \"\"target/@attachment@\"\" \" "
The script runs, but I get errors like the following. Some of the attachments have titles matching the issue they are assigned to, so I was able to see where there was a disconnect:
Client error: Attachment 'Blah-blah-blah-FOO-2866.xlsx' not found for issue FOO-2864 org.swift.common.cli.CliClient$ClientException: Attachment 'Blah-blah-blah-FOO-2866.xlsx' not found for issue FOO-2864
I was able to verify that the attachment does exist on FOO-2866, and not FOO-2864. Tips?
Had a related question:
Is there a way to use Jira CLI to download attachments specified in the file you get from getAttachmentList? For example, with use runFromAttachmentList? The --file option for that seems to imply the output as opposed to the input.
I was able to do it this way, but I'd prefer not to login/logout so many times:
for i in `cut -d \" -f 2 attachments.csv | sort -u`; do ./jira.sh --action runFromAttachmentList --issue $i --common "-a getAttachment --file \"target/@attachment@\" --name \"@attachment@\" --issue $i"; done
Lastly, regarding testing problems with I encountered with the example you gave me. It looks like the @attachment@ variables don't clear when script moves to next issue. Output shows success for the first issue, then failures for the rest. Is there a way to flush/clear a variable between iterations?
I believe there is a regression error in 3.9, try using release 3.8 until it is fixed in 4.0.
Regarding the other information, I would recommend adding a comment immediately after adding the issue with whatever details you want. JIRA doesn't provide any other way to associate a comment for a specific attachment.
Thanks Bob -- version 3.8 seems to work as expected. You sir rock!
What I meant earlier wasn't regarding comments specificially. I meant that if an attachment in the original issue had a timestamp and user associated with it, is it possible to recreate that data via your tool?
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 ...
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot