Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

To send an attachment there is two options, Multipart form data - this is what most systems use to work with attachments. Second option is Body this is where the remote system requires the content of the attachment to be included in the body.

For JSM comment see this tutorialSend only public comments from Jira Service Management

Body data

Use this method to send the content of the attachment as base64encoded in the body of the request.

Attachment is accessible via {{attachments}} variable, this is a list of attachments. To grab the first, last or latest use the syntax below:

  • {{attachments.first}}

  • {{attachments.last}} same as latest

  • {{attachments.latest}}

...

Properties on a attachment:

  • content type String base64encoded, ex {{attachments.last.content}}

  • authorKey type String, ex {{attachments.last.authorKey}}

  • authorObject type ApplicationUser, ex {{attachments.last.authorObject.username}}

  • created type Timestamp, ex {{attachments.last.created}}

  • filename type String, ex {{attachments.last.filename}}

  • filesize type Long, ex {{attachments.last.filesize}}

  • id type Long, ex {{attachments.last.id}}

  • mimetype type String, ex {{attachments.last.mimetype}}

  • zip type Boolean, ex {{attachments.last.zip}}

Multipart data - form data

Info

Usage note!

Use this only in the case were attachment is needed, since the payload is different than regular application/json types.

Info

Download sample configuration for attaching a file to a ticket from an incoming rule here and import it.

iHub can send attachments to external endpoints. This is done. by sendingĀ Content-Type: multipart/form-data.

...