Automation Failing - Attachment not coming over when required in new ticket

Question

Using Jira Cloud.

I am building an expense approval workflow, and part of that is an automation for pre-approval tickets to create a refular expense approval ticket when it hits a certain status. No issues there.

Where I am having issues is that an attachment is a required field in the pre-approval and regualr approval expense tickets. But when the automation fires when the pre-approval ticket hits the approved stage, it should generate the regaular approval ticket, copying over all fields.

I am getting an errir that the new ticket couldn't be created because there was no attachment.

Is this an order of operations thing?

Screen shot attached of error and rules.

Note, i have seperate workflows for teh two different ticket types. I am thinking maybe make the attachment not required on the regaulr approval workflow until it gets to a later stage. But I would still like to copy over the original attachment

Duc Thang TRAN · Accepted Answer

Hello @philipf

I think the transition (creation a ticket type: Expense Reimbursement ) has a condition that "Attachment" is required.

I not sure but somehow the action "Create issue" with copy attachment from trigger issues is conflicting, and may not align with the expected order of operations, as you mentioned.

Can you check this part? If an attachment requirement exists, you may need to delete it in order to create a new issue.

philipf · Accepted Answer

I was able to get this to work, and then both tickets disappeared simply creating two workflows for each ticket type. The tickets were created and when I went back to the board both were gone,

and got this error message,

Action details:

Issue condition

The following issues passed:

EX-48

Create issue

Issues created successfully

EX-49

Transition issue

Destination status could not be resolved. If using a smart-value ensure this resolves to a numeric status ID or untranslated name for issues (with current status):

EX-48 (Expense Approved - 10338)
I don't understand why the destination issue could be, it is the same workflow, and this wasn't an error issue when I had both ticket types of the same workflow (my issue was an order of operation using the same flow).