Atlassian Issue Tracker API

openapi: 3.2.0
info:
  title: Atlassian Bitbucket Issue Tracker API
  description: Code against the Bitbucket API to automate simple tasks, embed Bitbucket data into your own site, build mobile or desktop apps, or even add custom UI add-ons into Bitbucket itself using the Connect framework.
  version: '2.0'
  termsOfService: https://www.atlassian.com/legal/customer-agreement
  contact:
    name: Bitbucket Support
    url: https://support.atlassian.com/bitbucket-cloud/
    email: support@bitbucket.org
servers:
- url: https://api.bitbucket.org/2.0
tags:
- name: Issue Tracker
paths:
  /repositories/{workspace}/{repo_slug}/components:
    parameters:
    - name: repo_slug
      in: path
      description: 'This can either be the repository slug or the UUID of the repository,

        surrounded by curly-braces, for example: `{repository UUID}`.

        '
      required: true
      schema:
        type: string
    - name: workspace
      in: path
      description: 'This can either be the workspace ID (slug) or the workspace UUID

        surrounded by curly-braces, for example: `{workspace UUID}`.

        '
      required: true
      schema:
        type: string
    get:
      tags:
      - Issue Tracker
      description: Returns the components that have been defined in the issue tracker.<br><br>This resource is only available on repositories that have the issue<br>tracker enabled.
      summary: Atlassian List Components
      responses:
        '200':
          description: The components that have been defined in the issue tracker.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/paginated_components'
        '404':
          description: The specified repository does not exist or does not have the issue tracker enabled.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/error'
      security:
      - oauth2:
        - issue
      - basic: []
      - api_key: []
      operationId: atlassianListComponents
  /repositories/{workspace}/{repo_slug}/components/{component_id}:
    parameters:
    - name: component_id
      in: path
      description: The component's id
      required: true
      schema:
        type: integer
    - name: repo_slug
      in: path
      description: 'This can either be the repository slug or the UUID of the repository,

        surrounded by curly-braces, for example: `{repository UUID}`.

        '
      required: true
      schema:
        type: string
    - name: workspace
      in: path
      description: 'This can either be the workspace ID (slug) or the workspace UUID

        surrounded by curly-braces, for example: `{workspace UUID}`.

        '
      required: true
      schema:
        type: string
    get:
      tags:
      - Issue Tracker
      description: Returns the specified issue tracker component object.
      summary: Atlassian Get A Component For Issues
      responses:
        '200':
          description: The specified component object.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/component'
        '404':
          description: The specified repository or component does not exist or does not have the issue tracker enabled.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/error'
      security:
      - oauth2:
        - issue
      - basic: []
      - api_key: []
      operationId: atlassianGetAComponentForIssues
  /repositories/{workspace}/{repo_slug}/issues:
    parameters:
    - name: repo_slug
      in: path
      description: 'This can either be the repository slug or the UUID of the repository,

        surrounded by curly-braces, for example: `{repository UUID}`.

        '
      required: true
      schema:
        type: string
    - name: workspace
      in: path
      description: 'This can either be the workspace ID (slug) or the workspace UUID

        surrounded by curly-braces, for example: `{workspace UUID}`.

        '
      required: true
      schema:
        type: string
    get:
      tags:
      - Issue Tracker
      description: Returns the issues in the issue tracker.
      summary: Atlassian List Issues
      responses:
        '200':
          description: A paginated list of the issues matching any filter criteria that were provided.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/paginated_issues'
        '404':
          description: The specified repository does not exist or does not have the issue tracker enabled.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/error'
      security:
      - oauth2:
        - issue
      - basic: []
      - api_key: []
      operationId: atlassianListIssues
    post:
      tags:
      - Issue Tracker
      description: Creates a new issue.<br><br>This call requires authentication. Private repositories or private<br>issue trackers require the caller to authenticate with an account that<br>has appropriate authorization.<br><br>The authenticated user is used for the issue's `reporter` field.
      summary: Atlassian Create An Issue
      responses:
        '201':
          description: The newly created issue.
          headers:
            Location:
              description: The (absolute) URL of the newly created issue.
              schema:
                type: string
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/issue'
        '401':
          description: When the request wasn't authenticated.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/error'
        '403':
          description: When the authenticated user isn't authorized to create the issue.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/error'
        '404':
          description: The specified repository does not exist or does not have the issue tracker enabled.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/error'
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/issue'
        description: The new issue. The only required element is `title`. All other elements can be omitted from the body.
        required: true
      security:
      - oauth2:
        - issue:write
      - basic: []
      - api_key: []
      operationId: atlassianCreateAnIssue
  /repositories/{workspace}/{repo_slug}/issues/export:
    parameters:
    - name: repo_slug
      in: path
      description: 'This can either be the repository slug or the UUID of the repository,

        surrounded by curly-braces, for example: `{repository UUID}`.

        '
      required: true
      schema:
        type: string
    - name: workspace
      in: path
      description: 'This can either be the workspace ID (slug) or the workspace UUID

        surrounded by curly-braces, for example: `{workspace UUID}`.

        '
      required: true
      schema:
        type: string
    post:
      tags:
      - Issue Tracker
      description: A POST request to this endpoint initiates a new background celery task that archives the repo's issues.<br><br>When the job has been accepted, it will return a 202 (Accepted) along with a unique url to this job in the<br>'Location' response header. This url is the endpoint for where the user can obtain their zip files."
      summary: Atlassian Export Issues
      responses:
        '202':
          description: The export job has been accepted
        '401':
          description: The request wasn't authenticated properly
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/error'
        '403':
          description: When the authenticated user does not have admin permission on the repo
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/error'
        '404':
          description: The repo does not exist or does not have an issue tracker
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/error'
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/export_options'
        description: The options to apply to the export. Available options include `project_key` and `project_name` which, if specified, are used as the project key and name in the exported Jira json format. Option `send_email` specifies whether an email should be sent upon export result. Option `include_attachments` specifies whether attachments are included in the export.
      security:
      - oauth2:
        - issue
        - repository:admin
      - basic: []
      - api_key: []
      operationId: atlassianExportIssues
  /repositories/{workspace}/{repo_slug}/issues/export/{repo_name}-issues-{task_id}.zip:
    parameters:
    - name: repo_name
      in: path
      description: The name of the repo
      required: true
      schema:
        type: string
    - name: repo_slug
      in: path
      description: 'This can either be the repository slug or the UUID of the repository,

        surrounded by curly-braces, for example: `{repository UUID}`.

        '
      required: true
      schema:
        type: string
    - name: task_id
      in: path
      description: The ID of the export task
      required: true
      schema:
        type: string
    - name: workspace
      in: path
      description: 'This can either be the workspace ID (slug) or the workspace UUID

        surrounded by curly-braces, for example: `{workspace UUID}`.

        '
      required: true
      schema:
        type: string
    get:
      tags:
      - Issue Tracker
      description: This endpoint is used to poll for the progress of an issue export<br>job and return the zip file after the job is complete.<br>As long as the job is running, this will return a 202 response<br>with in the response body a description of the current status.<br><br>After the job has been scheduled, but before it starts executing, the endpoint<br>returns a 202 response with status `ACCEPTED`.<br><br>Once it starts running, it is a 202 response with status `STARTED` and progress filled.<br><br>After it is finished, it becomes a 200 response with status `SUCCESS` or `FAILURE`.
      summary: Atlassian Check Issue Export Status
      responses:
        '202':
          description: Export job accepted
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/issue_job_status'
              examples:
                response:
                  value:
                    type: issue_job_status
                    status: ACCEPTED
                    phase: Initializing
                    total: 0
                    count: 0
                    pct: 0
        '401':
          description: The request wasn't authenticated properly
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/error'
        '403':
          description: When the authenticated user does not have admin permission on the repo
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/error'
        '404':
          description: No export job has begun
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/error'
      security:
      - oauth2:
        - issue
        - repository:admin
      - basic: []
      - api_key: []
      operationId: atlassianCheckIssueExportStatus
  /repositories/{workspace}/{repo_slug}/issues/import:
    parameters:
    - name: repo_slug
      in: path
      description: 'This can either be the repository slug or the UUID of the repository,

        surrounded by curly-braces, for example: `{repository UUID}`.

        '
      required: true
      schema:
        type: string
    - name: workspace
      in: path
      description: 'This can either be the workspace ID (slug) or the workspace UUID

        surrounded by curly-braces, for example: `{workspace UUID}`.

        '
      required: true
      schema:
        type: string
    get:
      tags:
      - Issue Tracker
      description: When using GET, this endpoint reports the status of the current import task.<br><br>After the job has been scheduled, but before it starts executing, the endpoint<br>returns a 202 response with status `ACCEPTED`.<br><br>Once it starts running, it is a 202 response with status `STARTED` and progress filled.<br><br>After it is finished, it becomes a 200 response with status `SUCCESS` or `FAILURE`.
      summary: Atlassian Check Issue Import Status
      responses:
        '200':
          description: Import job complete with either FAILURE or SUCCESS status
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/issue_job_status'
        '202':
          description: Import job started
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/issue_job_status'
              examples:
                response:
                  value:
                    type: issue_job_status
                    status: ACCEPTED
                    phase: Attachments
                    total: 15
                    count: 0
                    percent: 0
        '401':
          description: The request wasn't authenticated properly
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/error'
        '403':
          description: When the authenticated user does not have admin permission on the repo
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/error'
        '404':
          description: No export job has begun
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/error'
      security:
      - oauth2:
        - issue:write
        - repository:admin
      - basic: []
      - api_key: []
      operationId: atlassianCheckIssueImportStatus
    post:
      tags:
      - Issue Tracker
      description: A POST request to this endpoint will import the zip file given by the archive parameter into the repository. All<br>existing issues will be deleted and replaced by the contents of the imported zip file.<br><br>Imports are done through a multipart/form-data POST. There is one valid and required form field, with the name<br>"archive," which needs to be a file field:<br><br>```<br>$ curl -u  -X POST -F archive=@/path/to/file.zip https://api.bitbucket.org/2.0/repositories///issues/import<br>```
      summary: Atlassian Import Issues
      responses:
        '202':
          description: Import job accepted
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/issue_job_status'
              examples:
                response:
                  value:
                    type: issue_job_status
                    status: ACCEPTED
                    phase: Attachments
                    total: 15
                    count: 0
                    percent: 0
        '401':
          description: The request wasn't authenticated properly
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/error'
        '403':
          description: When the authenticated user does not have admin permission on the repo
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/error'
        '404':
          description: No export job has begun
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/error'
        '409':
          description: Import already running
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/error'
      security:
      - oauth2:
        - issue:write
        - repository:admin
      - basic: []
      - api_key: []
      operationId: atlassianImportIssues
  /repositories/{workspace}/{repo_slug}/issues/{issue_id}:
    parameters:
    - name: issue_id
      in: path
      description: The issue id
      required: true
      schema:
        type: string
    - name: repo_slug
      in: path
      description: 'This can either be the repository slug or the UUID of the repository,

        surrounded by curly-braces, for example: `{repository UUID}`.

        '
      required: true
      schema:
        type: string
    - name: workspace
      in: path
      description: 'This can either be the workspace ID (slug) or the workspace UUID

        surrounded by curly-braces, for example: `{workspace UUID}`.

        '
      required: true
      schema:
        type: string
    delete:
      tags:
      - Issue Tracker
      description: Deletes the specified issue. This requires write access to the<br>repository.
      summary: Atlassian Delete An Issue
      responses:
        '200':
          description: The issue object.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/issue'
        '403':
          description: When the authenticated user isn't authorized to delete the issue.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/error'
        '404':
          description: The specified repository or issue does not exist or does not have the issue tracker enabled.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/error'
      security:
      - oauth2:
        - issue:write
      - basic: []
      - api_key: []
      operationId: atlassianDeleteAnIssue
    get:
      tags:
      - Issue Tracker
      description: Returns the specified issue.
      summary: Atlassian Get An Issue
      responses:
        '200':
          description: The issue object.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/issue'
        '403':
          description: When the authenticated user isn't authorized to access the issue.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/error'
        '404':
          description: The specified repository or issue does not exist or does not have the issue tracker enabled.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/error'
        '410':
          description: The specified issue is unavailable.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/error'
      security:
      - oauth2:
        - issue
      - basic: []
      - api_key: []
      operationId: atlassianGetAnIssue
    put:
      tags:
      - Issue Tracker
      description: 'Modifies the issue.<br><br>```<br>$ curl https://api.bitbucket.org/2.0/repostories/evzijst/dogslow/issues/123 \<br>  -u evzijst -s -X PUT -H ''Content-Type: application/json'' \<br>  -d ''{<br>  "title": "Updated title",<br>  "assignee": {<br>    "account_id": "5d5355e8c6b9320d9ea5b28d"<br>  },<br>  "priority": "minor",<br>  "version": {<br>    "name": "1.0"<br>  },<br>  "component": null<br>}''<br>```<br><br>This example changes the `title`, `assignee`, `priority` and the<br>`version`. It also removes the value of the `component` from the issue<br>by setting the field to `null`. Any field not present keeps its existing<br>value.<br><br>Each time an issue is edited in the UI or through the API, an immutable<br>change record is created under the `/issues/123/changes` endpoint. It<br>also has a comment associated with the change.'
      summary: Atlassian Update An Issue
      responses:
        '200':
          description: The updated issue object.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/issue'
        '403':
          description: When the authenticated user isn't authorized to access the issue.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/error'
        '404':
          description: The specified repository or issue does not exist or does not have the issue tracker enabled.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/error'
      security:
      - oauth2:
        - issue:write
      - basic: []
      - api_key: []
      operationId: atlassianUpdateAnIssue
  /repositories/{workspace}/{repo_slug}/issues/{issue_id}/attachments:
    parameters:
    - name: issue_id
      in: path
      description: The issue id
      required: true
      schema:
        type: string
    - name: repo_slug
      in: path
      description: 'This can either be the repository slug or the UUID of the repository,

        surrounded by curly-braces, for example: `{repository UUID}`.

        '
      required: true
      schema:
        type: string
    - name: workspace
      in: path
      description: 'This can either be the workspace ID (slug) or the workspace UUID

        surrounded by curly-braces, for example: `{workspace UUID}`.

        '
      required: true
      schema:
        type: string
    get:
      tags:
      - Issue Tracker
      description: Returns all attachments for this issue.<br><br>This returns the files' meta data. This does not return the files'<br>actual contents.<br><br>The files are always ordered by their upload date.
      summary: Atlassian List Attachments For An Issue
      responses:
        '200':
          description: A paginated list of all attachments for this issue.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/paginated_issue_attachments'
        '401':
          description: If the issue tracker is private and the request was not authenticated.
        '404':
          description: The specified repository or issue does not exist or does not have the issue tracker enabled.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/error'
      security:
      - oauth2:
        - issue
      - basic: []
      - api_key: []
      operationId: atlassianListAttachmentsForAnIssue
    post:
      tags:
      - Issue Tracker
      description: Upload new issue attachments.<br><br>To upload files, perform a `multipart/form-data` POST containing one<br>or more file fields.<br><br>When a file is uploaded with the same name as an existing attachment,<br>then the existing file will be replaced.
      summary: Atlassian Upload An Attachment To An Issue
      responses:
        '201':
          description: An empty response document.
          headers:
            Location:
              description: The URL to the issue's collection of attachments.
              schema:
                type: string
        '400':
          description: If no files were uploaded, or if the wrong `Content-Type` was used.
        '401':
          description: If the issue tracker is private and the request was not authenticated.
        '404':
          description: The specified repository or issue does not exist or does not have the issue tracker enabled.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/error'
      security:
      - oauth2:
        - issue:write
      - basic: []
      - api_key: []
      operationId: atlassianUploadAnAttachmentToAnIssue
  /repositories/{workspace}/{repo_slug}/issues/{issue_id}/attachments/{path}:
    parameters:
    - name: issue_id
      in: path
      description: The issue id
      required: true
      schema:
        type: string
    - name: path
      in: path
      description: Path to the file.
      required: true
      schema:
        type: string
    - name: repo_slug
      in: path
      description: 'This can either be the repository slug or the UUID of the repository,

        surrounded by curly-braces, for example: `{repository UUID}`.

        '
      required: true
      schema:
        type: string
    - name: workspace
      in: path
      description: 'This can either be the workspace ID (slug) or the workspace UUID

        surrounded by curly-braces, for example: `{workspace UUID}`.

        '
      required: true
      schema:
        type: string
    delete:
      tags:
      - Issue Tracker
      description: Deletes an attachment.
      summary: Atlassian Delete An Attachment For An Issue
      responses:
        '204':
          description: Indicates that the deletion was successful
        '401':
          description: If the issue tracker is private and the request was not authenticated.
        '404':
          description: The specified repository or issue does not exist or does not have the issue tracker enabled.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/error'
      security:
      - oauth2:
        - issue:write
      - basic: []
      - api_key: []
      operationId: atlassianDeleteAnAttachmentForAnIssue
    get:
      tags:
      - Issue Tracker
      description: Returns the contents of the specified file attachment.<br><br>Note that this endpoint does not return a JSON response, but instead<br>returns a redirect pointing to the actual file that in turn will return<br>the raw contents.<br><br>The redirect URL contains a one-time token that has a limited lifetime.<br>As a result, the link should not be persisted, stored, or shared.
      summary: Atlassian Get Attachment For An Issue
      responses:
        '302':
          description: A redirect to the file's contents
          headers:
            Location:
              schema:
                type: string
        '401':
          description: If the issue tracker is private and the request was not authenticated.
        '404':
          description: The specified repository or issue does not exist or does not have the issue tracker enabled.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/error'
      security:
      - oauth2:
        - issue
      - basic: []
      - api_key: []
      operationId: atlassianGetAttachmentForAnIssue
  /repositories/{workspace}/{repo_slug}/issues/{issue_id}/changes:
    parameters:
    - name: issue_id
      in: path
      description: The issue id
      required: true
      schema:
        type: string
    - name: repo_slug
      in: path
      description: 'This can either be the repository slug or the UUID of the repository,

        surrounded by curly-braces, for example: `{repository UUID}`.

        '
      required: true
      schema:
        type: string
    - name: workspace
      in: path
      description: 'This can either be the workspace ID (slug) or the workspace UUID

        surrounded by curly-braces, for example: `{workspace UUID}`.

        '
      required: true
      schema:
        type: string
    get:
      tags:
      - Issue Tracker
      description: Returns the list of all changes that have been made to the specified<br>issue. Changes are returned in chronological order with the oldest<br>change first.<br><br>Each time an issue is edited in the UI or through the API, an immutable<br>change record is created under the `/issues/123/changes` endpoint. It<br>also has a comment associated with the change.<br><br>Note that this operation is changing significantly, due to privacy changes.<br>See the [announcement](https://developer.atlassian.com/cloud/bitbucket/bitbucket-api-changes-gdpr/#changes-to-the-issue-changes-api)<br>for details.<br><br>Changes support [filtering and sorting](/cloud/bitbucket/rest/intro/#filtering) that<br>can be used to search for specific changes. For instance, to see<br>when an issue transitioned to "resolved":<br><br>```<br>$ curl -s https://api.bitbucket.org/2.0/repositories/site/master/issues/1/changes \<br>   -G --data-urlencode='q=changes.state.new = "resolved"'<br>```<br><br>This resource is only available on repositories that have the issue<br>tracker enabled.<br><br>N.B.<br><br>The `changes.assignee` and `changes.assignee_account_id` fields are not<br>a `user` object. Instead, they contain the raw `username` and<br>`account_id` of the user. This is to protect the integrity of the audit<br>log even after a user account gets deleted.<br><br>The `changes.assignee` field is deprecated will disappear in the<br>future. Use `changes.assignee_account_id` instead.
      summary: Atlassian List Changes On An Issue
      responses:
        '200':
          description: Returns all the issue changes that were made on the specified issue.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/paginated_log_entries'
              examples:
                response:
                  value:
                    pagelen: 20
                    values:
                    - changes:
                        priority:
                          new: trivial
                          old: major
                        assignee:
                          new: ''
                          old: evzijst
                        assignee_account_id:
                          new: ''
                          old: 557058:c0b72ad0-1cb5-4018-9cdc-0cde8492c443
                        kind:
                          new: enhancement
                          old: bug
                      links:
                        self:
                          href: https://api.bitbucket.org/2.0/repositories/evzijst/dogslow/issues/1/changes/2
                        html:
                          href: https://bitbucket.org/evzijst/dogslow/issues/1#comment-2
                      issue:
                        links:
                          self:
                            href: https://api.bitbucket.org/2.0/repositories/evzijst/dogslow/issues/1
                        type: issue
                        id: 1
                        repository:
                          links:
                            self:
                              href: https://api.bitbucket.org/2.0/repositories/evzijst/dogslow
                            html:
                              href: https://bitbucket.org/evzijst/dogslow
                            avatar:
                              href: https://bitbucket.org/evzijst/dogslow/avatar/32/
                          type: repository
                          name: dogslow
                          full_name: evzijst/dogslow
                          uuid: '{988b17c6-1a47-4e70-84ee-854d5f012bf6}'
                        title: Updated title
                      created_on: '2018-03-03T00:35:28.353630+00:00'
                      user:
                        username: evzijst
                        nickname: evzijst
                        display_name: evzijst
                        type: user
                        uuid: '{aaa7972b-38af-4fb1-802d-6e3854c95778}'
                        links:
                          self:
                            href: https://api.bitbucket.org/2.0/users/evzijst
                          html:
                            href: https://bitbucket.org/evzijst/
                          avatar:
                            href: https://bitbucket.org/account/evzijst/avatar/32/
                      message:
                        raw: Removed assignee, changed kind and priority.
                        markup: markdown
                        html: <p>Removed assignee, changed kind and priority.</p>
                        type: rendered
                      type: issue_change
                      id: 2
                    page: 1
        '404':
          description: The specified repository or issue does not exist or does not have the is

# --- truncated at 32 KB (209 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/atlassian/refs/heads/main/openapi/atlassian-issue-tracker-api-openapi.yml