Upload an attachment to an issue

Deprecated

POST

/repositories/{workspace}/{repo_slug}/issues/{issue_id}/attachments

Upload new issue attachments.

To upload files, perform a multipart/form-data POST containing one or more file fields.

When a file is uploaded with the same name as an existing attachment, then the existing file will be replaced.

Authorizations

• oauth2
  issue:write
• basic
• api_key

Parameters

Path Parameters

issue_id

required

string

The issue id

repo_slug

required

string

This can either be the repository slug or the UUID of the repository, surrounded by curly-braces, for example: {repository UUID}.

workspace

required

string

This can either be the workspace ID (slug) or the workspace UUID surrounded by curly-braces, for example: {workspace UUID}.

Responses

201

An empty response document.

Headers

Location

string

The URL to the issue’s collection of attachments.

400

If no files were uploaded, or if the wrong Content-Type was used.

401

If the issue tracker is private and the request was not authenticated.

404

The specified repository or issue does not exist or does not have the issue tracker enabled.

Media type application/json

Error

Base type for most resource objects. It defines the common type element that identifies an object’s type. It also identifies the element as Swagger’s discriminator.

object

type

required

string

error

object

message

required

string

detail

string

data

Optional structured data that is endpoint-specific.

object

key

additional properties

any

key

additional properties

any

Example ^generated

{
  "type": "example",
  "error": {
    "message": "example",
    "detail": "example",
    "data": {}
  }
}