Atlassian Issues API

openapi: 3.2.0
info:
  contact:
    email: ecosystem@atlassian.com
  description: Jira Cloud platform REST API documentation
  license:
    name: Apache 2.0
    url: http://www.apache.org/licenses/LICENSE-2.0.html
  termsOfService: http://atlassian.com/terms/
  title: Atlassian The Jira Cloud platform REST Issues API
  version: 1001.0.0-SNAPSHOT-67b5c6e5f3598d7ec1649016d026468ab2838a77
servers:
- url: https://your-domain.atlassian.net
tags:
- description: "This resource represents Jira issues. Use it to:\n\n *  create or edit issues, individually or in bulk.\n *  retrieve metadata about the options for creating or editing issues.\n *  delete an issue.\n *  assign a user to an issue.\n *  get issue changelogs.\n *  send notifications about an issue.\n *  get details of the transitions available for an issue.\n *  transition an issue.\n *  Archive issues.\n *  Unarchive issues.\n *  Export archived issues."
  name: Issues
paths:
  /rest/api/3/events:
    get:
      deprecated: false
      description: Returns all issue events.<br><br>**[Permissions](#permissions) required:** *Administer Jira* [global permission](https://confluence.atlassian.com/x/x4dKLg).
      operationId: atlassianGetevents
      parameters: []
      responses:
        '200':
          content:
            application/json:
              example: '[{"id":1,"name":"Issue Created"},{"id":2,"name":"Issue Updated"}]'
              schema:
                items:
                  $ref: '#/components/schemas/IssueEvent'
                type: array
          description: Returned if the request is successful.
        '401':
          description: Returned if the authentication credentials are incorrect or missing.
        '403':
          description: Returned if the user does not have permission to complete this request.
      security:
      - basicAuth: []
      - OAuth2:
        - manage:jira-configuration
      summary: Atlassian Get Events
      tags:
      - Issues
      x-atlassian-data-security-policy:
      - app-access-rule-exempt: true
      x-atlassian-oauth2-scopes:
      - scheme: OAuth2
        scopes:
        - manage:jira-configuration
        state: Current
      - scheme: OAuth2
        scopes:
        - read:issue-event:jira
        state: Beta
      x-experimental: true
      x-atlassian-connect-scope: ADMIN
  /rest/api/3/issue:
    post:
      deprecated: false
      description: Creates an issue or, where the option to create subtasks is enabled in Jira, a subtask. A transition may be applied, to move the issue or subtask to a workflow step other than the default start step, and issue properties set.<br><br>The content of the issue or subtask is defined using `update` and `fields`. The fields that can be set in the issue or subtask are determined using the [ Get create issue metadata](#api-rest-api-3-issue-createmeta-get). These are the same fields that appear on the issue's create screen. Note that the `description`, `environment`, and any `textarea` type custom fields (multi-line text fields) take Atlassian Document Format content. Single line custom fields (`textfield`) accept a string and don't handle Atlassian Document Format content.<br><br>Creating a subtask differs from creating an issue as follows:<br><br> *  `issueType` must be set to a subtask issue type (use [ Get create issue metadata](#api-rest-api-3-issue-createmeta-get) to find subtask issue types).<br> *  `parent` must contain the ID or key of the parent issue.<br><br>In a next-gen project any issue may be made a child providing that the parent and child are members of the same project.<br><br>**[Permissions](#permissions) required:** *Browse projects* and *Create issues* [project permissions](https://confluence.atlassian.com/x/yodKLg) for the project in which the issue or subtask is created.
      operationId: atlassianCreateissue
      parameters:
      - description: Whether the project in which the issue is created is added to the user's **Recently viewed** project list, as shown under **Projects** in Jira. When provided, the issue type and request type are added to the user's history for a project. These values are then used to provide defaults on the issue create screen.
        in: query
        name: updateHistory
        schema:
          default: false
          type: boolean
      requestBody:
        content:
          application/json:
            example:
              fields:
                assignee:
                  id: 5b109f2e9729b51b54dc274d
                components:
                - id: '10000'
                customfield_10000: 09/Jun/19
                customfield_20000: 06/Jul/19 3:25 PM
                customfield_30000:
                - '10000'
                - '10002'
                customfield_40000:
                  content:
                  - content:
                    - text: Occurs on all orders
                      type: text
                    type: paragraph
                  type: doc
                  version: 1
                customfield_50000:
                  content:
                  - content:
                    - text: Could impact day-to-day work.
                      type: text
                    type: paragraph
                  type: doc
                  version: 1
                customfield_60000: jira-software-users
                customfield_70000:
                - jira-administrators
                - jira-software-users
                customfield_80000:
                  value: red
                description:
                  content:
                  - content:
                    - text: Order entry fails when selecting supplier.
                      type: text
                    type: paragraph
                  type: doc
                  version: 1
                duedate: '2019-05-11'
                environment:
                  content:
                  - content:
                    - text: UAT
                      type: text
                    type: paragraph
                  type: doc
                  version: 1
                fixVersions:
                - id: '10001'
                issuetype:
                  id: '10000'
                labels:
                - bugfix
                - blitz_test
                parent:
                  key: PROJ-123
                priority:
                  id: '20000'
                project:
                  id: '10000'
                reporter:
                  id: 5b10a2844c20165700ede21g
                security:
                  id: '10000'
                summary: Main order flow broken
                timetracking:
                  originalEstimate: '10'
                  remainingEstimate: '5'
                versions:
                - id: '10000'
              update: {}
            schema:
              $ref: '#/components/schemas/IssueUpdateDetails'
        required: true
      responses:
        '201':
          content:
            application/json:
              example: '{"id":"10000","key":"ED-24","self":"https://your-domain.atlassian.net/rest/api/3/issue/10000","transition":{"status":200,"errorCollection":{"errorMessages":[],"errors":{}}}}'
              schema:
                $ref: '#/components/schemas/CreatedIssue'
          description: Returned if the request is successful.
        '400':
          content:
            application/json:
              example: '{"errorMessages":["Field ''priority'' is required"],"errors":{}}'
              schema:
                $ref: '#/components/schemas/ErrorCollection'
          description: "Returned if the request:\n\n *  is missing required fields.\n *  contains invalid field values.\n *  contains fields that cannot be set for the issue type.\n *  is by a user who does not have the necessary permission.\n *  is to create a subtype in a project different that of the parent issue.\n *  is for a subtask when the option to create subtasks is disabled.\n *  is invalid for any other reason."
        '401':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorCollection'
          description: Returned if the authentication credentials are incorrect or missing.
        '403':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorCollection'
          description: Returned if the user does not have the necessary permission.
        '422':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorCollection'
          description: Returned if a configuration problem prevents the creation of the issue. (refer to the [changelog](https://developer.atlassian.com/changelog/#CHANGE-1364) *for more details.*
      security:
      - basicAuth: []
      - OAuth2:
        - write:jira-work
      - {}
      summary: Atlassian Create Issue
      tags:
      - Issues
      x-atlassian-data-security-policy:
      - app-access-rule-exempt: false
      x-atlassian-oauth2-scopes:
      - scheme: OAuth2
        scopes:
        - write:jira-work
        state: Current
      - scheme: OAuth2
        scopes:
        - write:issue:jira
        - write:comment:jira
        - write:comment.property:jira
        - write:attachment:jira
        - read:issue:jira
        state: Beta
      x-atlassian-connect-scope: WRITE
  /rest/api/3/issue/archive:
    post:
      deprecated: false
      description: 'Enables admins to archive up to 100,000 issues in a single request using JQL, returning the URL to check the status of the submitted request.<br><br>You can use the [get task](https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-tasks/#api-rest-api-3-task-taskid-get) and [cancel task](https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-tasks/#api-rest-api-3-task-taskid-cancel-post) APIs to manage the request.<br><br>**Note that:**<br><br> *  you can''t archive subtasks directly, only through their parent issues<br> *  you can only archive issues from software, service management, and business projects<br><br>**[Permissions](#permissions) required:** Jira admin or site admin: [global permission](https://confluence.atlassian.com/x/x4dKLg)<br><br>**License required:** Premium or Enterprise<br><br>**Signed-in users only:** This API can''t be accessed anonymously.<br><br>**Rate limiting:** Only a single request per jira instance can be active at any given time.<br><br>  <br>'
      operationId: atlassianArchiveissuesasync
      parameters: []
      requestBody:
        content:
          application/json:
            example:
              jql: project = FOO AND updated < -2y
            schema:
              $ref: '#/components/schemas/ArchiveIssueAsyncRequest'
        description: A JQL query specifying the issues to archive. Note that subtasks can only be archived through their parent issues.
        required: true
      responses:
        '202':
          content:
            application/json:
              example: '"https://your-domain.atlassian.net/rest/api/3/task/1010"'
              schema:
                type: string
          description: Returns the URL to check the status of the submitted request.
        '400':
          content:
            application/json:
              example: '{"errorMessages":["Invalid JQL. Bad request."],"errors":{}}'
          description: Returned if no issues were archived due to a bad request, for example an invalid JQL query.
        '401':
          content:
            application/json:
              example: '{"errorMessages":["User is not logged in."],"errors":{}}'
          description: Returned if no issues were archived because the provided authentication credentials are either missing or invalid.
        '403':
          content:
            application/json:
              example: '{"errorMessages":["Archiving issues is only available for premium editions of Jira."],"errors":{}}'
          description: Returned if no issues were archived because the user lacks the required Jira admin or site admin permissions.
        '412':
          content:
            application/json:
              example: '{"errorMessages":["An issue archival task is already running with ID 1010. To start a new one, cancel the task or wait for it to finish."],"errors":{}}'
          description: Returned if a request to archive issue(s) is already running.
      security:
      - basicAuth: []
      - OAuth2:
        - write:jira-work
      - {}
      summary: Atlassian Archive Issue S By Jql
      tags:
      - Issues
      x-atlassian-data-security-policy:
      - app-access-rule-exempt: false
      x-atlassian-oauth2-scopes:
      - scheme: OAuth2
        scopes:
        - write:jira-work
        state: Current
      - scheme: OAuth2
        scopes:
        - write:issue:jira
        state: Beta
      x-experimental: true
      x-atlassian-connect-scope: WRITE
    put:
      deprecated: false
      description: 'Enables admins to archive up to 1000 issues in a single request using issue ID/key, returning details of the issue(s) archived in the process and the errors encountered, if any.<br><br>**Note that:**<br><br> *  you can''t archive subtasks directly, only through their parent issues<br> *  you can only archive issues from software, service management, and business projects<br><br>**[Permissions](#permissions) required:** Jira admin or site admin: [global permission](https://confluence.atlassian.com/x/x4dKLg)<br><br>**License required:** Premium or Enterprise<br><br>**Signed-in users only:** This API can''t be accessed anonymously.<br><br>  <br>'
      operationId: atlassianArchiveissues
      parameters: []
      requestBody:
        content:
          application/json:
            example:
              issueIdsOrKeys:
              - PR-1
              - '1001'
              - PROJECT-2
            schema:
              $ref: '#/components/schemas/IssueArchivalSyncRequest'
        description: Contains a list of issue keys or IDs to be archived.
        required: true
      responses:
        '200':
          content:
            application/json:
              example: '{"errors":{"issueIsSubtask":{"count":3,"issueIdsOrKeys":["ST-1","ST-2","ST-3"],"message":"Issue is subtask."},"issuesInArchivedProjects":{"count":2,"issueIdsOrKeys":["AR-1","AR-2"],"message":"Issue exists in archived project."},"issuesInUnlicensedProjects":{"count":3,"issueIdsOrKeys":["UL-1","UL-2","UL-3"],"message":"Issues with these IDs are in unlicensed projects."},"issuesNotFound":{"count":3,"issueIdsOrKeys":["PR-1","PR-2","PR-3"],"message":"Issue not found."}},"numberOfIssuesUpdated":10}'
              schema:
                $ref: '#/components/schemas/IssueArchivalSyncResponse'
          description: Returned if there is at least one valid issue to archive in the request. The return message will include the count of archived issues and subtasks, as well as error details for issues which failed to get archived.
        '400':
          content:
            application/json:
              example: '{"errorMessages":["No valid issue to archive or unarchive. Bad request."],"errors":{}}'
          description: "Returned if none of the issues in the request can be archived. Possible reasons:\n\n *  the issues weren't found\n *  the issues are subtasks\n *  the issues belong to unlicensed projects\n *  the issues belong to archived projects"
        '401':
          content:
            application/json:
              example: '{"errorMessages":["User is not logged in."],"errors":{}}'
          description: Returned if no issues were archived because the provided authentication credentials are either missing or invalid.
        '403':
          content:
            application/json:
              example: '{"errorMessages":["Only admins can archive or unarchive issues. Access denied."],"errors":{}}'
          description: Returned if no issues were archived because the user lacks the required Jira admin or site admin permissions.
        '412':
          content:
            application/json:
              example: '{"errorMessages":["The number of issues to archive or unarchive exceeds the hard limit of 1000. Precondition failed."],"errors":{}}'
          description: Returned if one or more issues were successfully archived, but the operation was incomplete because the number of issue IDs or keys provided exceeds 1000.
      security:
      - basicAuth: []
      - OAuth2:
        - write:jira-work
      - {}
      summary: Atlassian Archive Issue S By Issue Id Key
      tags:
      - Issues
      x-atlassian-data-security-policy:
      - app-access-rule-exempt: false
      x-atlassian-oauth2-scopes:
      - scheme: OAuth2
        scopes:
        - write:jira-work
        state: Current
      - scheme: OAuth2
        scopes:
        - write:issue:jira
        state: Beta
      x-experimental: true
      x-atlassian-connect-scope: WRITE
  /rest/api/3/issue/bulk:
    post:
      deprecated: false
      description: Creates upto **50** issues and, where the option to create subtasks is enabled in Jira, subtasks. Transitions may be applied, to move the issues or subtasks to a workflow step other than the default start step, and issue properties set.<br><br>The content of each issue or subtask is defined using `update` and `fields`. The fields that can be set in the issue or subtask are determined using the [ Get create issue metadata](#api-rest-api-3-issue-createmeta-get). These are the same fields that appear on the issues' create screens. Note that the `description`, `environment`, and any `textarea` type custom fields (multi-line text fields) take Atlassian Document Format content. Single line custom fields (`textfield`) accept a string and don't handle Atlassian Document Format content.<br><br>Creating a subtask differs from creating an issue as follows:<br><br> *  `issueType` must be set to a subtask issue type (use [ Get create issue metadata](#api-rest-api-3-issue-createmeta-get) to find subtask issue types).<br> *  `parent` the must contain the ID or key of the parent issue.<br><br>**[Permissions](#permissions) required:** *Browse projects* and *Create issues* [project permissions](https://confluence.atlassian.com/x/yodKLg) for the project in which each issue or subtask is created.
      operationId: atlassianCreateissues
      parameters: []
      requestBody:
        content:
          application/json:
            example:
              issueUpdates:
              - fields:
                  assignee:
                    id: 5b109f2e9729b51b54dc274d
                  components:
                  - id: '10000'
                  customfield_10000: 09/Jun/19
                  customfield_20000: 06/Jul/19 3:25 PM
                  customfield_30000:
                  - '10000'
                  - '10002'
                  customfield_40000:
                    content:
                    - content:
                      - text: Occurs on all orders
                        type: text
                      type: paragraph
                    type: doc
                    version: 1
                  customfield_50000:
                    content:
                    - content:
                      - text: Could impact day-to-day work.
                        type: text
                      type: paragraph
                    type: doc
                    version: 1
                  customfield_60000: jira-software-users
                  customfield_70000:
                  - jira-administrators
                  - jira-software-users
                  customfield_80000:
                    value: red
                  description:
                    content:
                    - content:
                      - text: Order entry fails when selecting supplier.
                        type: text
                      type: paragraph
                    type: doc
                    version: 1
                  duedate: '2011-03-11'
                  environment:
                    content:
                    - content:
                      - text: UAT
                        type: text
                      type: paragraph
                    type: doc
                    version: 1
                  fixVersions:
                  - id: '10001'
                  issuetype:
                    id: '10000'
                  labels:
                  - bugfix
                  - blitz_test
                  priority:
                    id: '20000'
                  project:
                    id: '10000'
                  reporter:
                    id: 5b10a2844c20165700ede21g
                  security:
                    id: '10000'
                  summary: Main order flow broken
                  timetracking:
                    originalEstimate: '10'
                    remainingEstimate: '5'
                  versions:
                  - id: '10000'
                update:
                  worklog:
                  - add:
                      started: 2019-07-05T11:05:00.000+0000
                      timeSpent: 60m
              - fields:
                  assignee:
                    id: 5b109f2e9729b51b54dc274d
                  components:
                  - id: '10000'
                  customfield_10000: 09/Jun/19
                  customfield_20000: 06/Jul/19 3:25 PM
                  customfield_30000:
                  - '10000'
                  - '10002'
                  customfield_40000:
                    content:
                    - content:
                      - text: Occurs on all orders
                        type: text
                      type: paragraph
                    type: doc
                    version: 1
                  customfield_50000:
                    content:
                    - content:
                      - text: Could impact day-to-day work.
                        type: text
                      type: paragraph
                    type: doc
                    version: 1
                  customfield_60000: jira-software-users
                  customfield_70000:
                  - jira-administrators
                  - jira-software-users
                  customfield_80000:
                    value: red
                  description:
                    content:
                    - content:
                      - text: Order remains pending after approved.
                        type: text
                      type: paragraph
                    type: doc
                    version: 1
                  duedate: '2019-04-16'
                  environment:
                    content:
                    - content:
                      - text: UAT
                        type: text
                      type: paragraph
                    type: doc
                    version: 1
                  fixVersions:
                  - id: '10001'
                  issuetype:
                    id: '10000'
                  labels:
                  - new_release
                  priority:
                    id: '20000'
                  project:
                    id: '1000'
                  reporter:
                    id: 5b10a2844c20165700ede21g
                  security:
                    id: '10000'
                  summary: Order stuck in pending
                  timetracking:
                    originalEstimate: '15'
                    remainingEstimate: '5'
                  versions:
                  - id: '10000'
                update: {}
            schema:
              $ref: '#/components/schemas/IssuesUpdateBean'
        required: true
      responses:
        '201':
          content:
            application/json:
              example: '{"issues":[{"id":"10000","key":"ED-24","self":"https://your-domain.atlassian.net/rest/api/3/issue/10000","transition":{"status":200,"errorCollection":{"errorMessages":[],"errors":{}}}},{"id":"10001","key":"ED-25","self":"https://your-domain.atlassian.net/rest/api/3/issue/10001"}],"errors":[]}'
              schema:
                $ref: '#/components/schemas/CreatedIssues'
          description: "Returned if any of the issue or subtask creation requests were successful. A request may be unsuccessful when it:\n\n *  is missing required fields.\n *  contains invalid field values.\n *  contains fields that cannot be set for the issue type.\n *  is by a user who does not have the necessary permission.\n *  is to create a subtype in a project different that of the parent issue.\n *  is for a subtask when the option to create subtasks is disabled.\n *  is invalid for any other reason."
        '400':
          content:
            application/json:
              example: '{"issues":[],"errors":[{"elementErrors":{"errorMessages":[],"errors":{"issuetype":"The issue type selected is invalid.","project":"Sub-tasks must be created in the same project as the parent."}},"failedElementNumber":0,"status":400},{"elementErrors":{"errorMessages":[],"errors":{"issuetype":"The issue type selected is invalid.","project":"Sub-tasks must be created in the same project as the parent."}},"failedElementNumber":1,"status":400}]}'
              schema:
                $ref: '#/components/schemas/CreatedIssues'
          description: "Returned if all requests are invalid. Requests may be unsuccessful when they:\n\n *  are missing required fields.\n *  contain invalid field values.\n *  contain fields that cannot be set for the issue type.\n *  are by a user who does not have the necessary permission.\n *  are to create a subtype in a project different that of the parent issue.\n *  is for a subtask when the option to create subtasks is disabled.\n *  are invalid for any other reason."
        '401':
          description: Returned if the authentication credentials are incorrect or missing.
      security:
      - basicAuth: []
      - OAuth2:
        - write:jira-work
      - {}
      summary: Atlassian Bulk Create Issue
      tags:
      - Issues
      x-atlassian-data-security-policy:
      - app-access-rule-exempt: false
      x-atlassian-oauth2-scopes:
      - scheme: OAuth2
        scopes:
        - write:jira-work
        state: Current
      - scheme: OAuth2
        scopes:
        - write:issue:jira
        - write:comment:jira
        - write:comment.property:jira
        - write:attachment:jira
        - read:issue:jira
        state: Beta
      x-atlassian-connect-scope: WRITE
  /rest/api/3/issue/createmeta:
    get:
      deprecated: true
      description: Returns details of projects, issue types within projects, and, when requested, the create screen fields for each issue type for the user. Use the information to populate the requests in [ Create issue](#api-rest-api-3-issue-post) and [Create issues](#api-rest-api-3-issue-bulk-post).<br><br>The request can be restricted to specific projects or issue types using the query parameters. The response will contain information for the valid projects, issue types, or project and issue type combinations requested. Note that invalid project, issue type, or project and issue type combinations do not generate errors.<br><br>This operation can be accessed anonymously.<br><br>**[Permissions](#permissions) required:** *Create issues* [project permission](https://confluence.atlassian.com/x/yodKLg) in the requested projects.
      operationId: atlassianGetcreateissuemeta
      parameters:
      - description: List of project IDs. This parameter accepts a comma-separated list. Multiple project IDs can also be provided using an ampersand-separated list. For example, `projectIds=10000,10001&projectIds=10020,10021`. This parameter may be provided with `projectKeys`.
        in: query
        name: projectIds
        schema:
          items:
            type: string
          type: array
      - description: List of project keys. This parameter accepts a comma-separated list. Multiple project keys can also be provided using an ampersand-separated list. For example, `projectKeys=proj1,proj2&projectKeys=proj3`. This parameter may be provided with `projectIds`.
        in: query
        name: projectKeys
        schema:
          items:
            type: string
          type: array
      - description: List of issue type IDs. This parameter accepts a comma-separated list. Multiple issue type IDs can also be provided using an ampersand-separated list. For example, `issuetypeIds=10000,10001&issuetypeIds=10020,10021`. This parameter may be provided with `issuetypeNames`.
        in: query
        name: issuetypeIds
        schema:
          items:
            type: string
          type: array
      - description: List of issue type names. This parameter accepts a comma-separated list. Multiple issue type names can also be provided using an ampersand-separated list. For example, `issuetypeNames=name1,name2&issuetypeNames=name3`. This parameter may be provided with `issuetypeIds`.
        in: query
        name: issuetypeNames
        schema:
          items:
            type: string
          type: array
      - description: Use [expand](#expansion) to include additional information about issue metadata in the response. This parameter accepts `projects.issuetypes.fields`, which returns information about the fields in the issue creation screen for each issue type. Fields hidden from the screen are not returned. Use the information to populate the `fields` and `update` fields in [Create issue](#api-rest-api-3-issue-post) and [Create issues](#api-rest-api-3-issue-bulk-post).
        in: query
        name: expand
        schema:
          type: string
      responses:
        '200':
          content:
            application/json:
              example: '{"projects":[{"avatarUrls":{"16x16":"https://your-domain.atlassian.net/secure/projectavatar?size=xsmall&pid=10000&avatarId=10011","24x24":"https://your-domain.atlassian.net/secure/projectavatar?size=small&pid=10000&avatarId=10011","32x32":"https://your-domain.atlassian.net/secure/projectavatar?size=medium&pid=10000&avatarId=10011","48x48":"https://your-domain.atlassian.net/secure/projectavatar?pid=10000&avatarId=10011"},"id":"10000","issuetypes":[{"description":"An error in the code","fields":{"issuetype":{"allowedValues":["set"],"autoCompleteUrl":"issuetype","hasDefaultValue":false,"key":"issuetype","name":"Issue Type","required":true}},"iconUrl":"https://your-domain.atlassian.net/images/icons/issuetypes/bug.png","id":"1","name":"Bug","self":"https://your-domain.atlassian.net/rest/api/3/issueType/1","subtask":false}],"key":"ED","name":"Edison Project","self":"https://your-domain.atlassian.net/rest/api/3/project/ED"}]}'
              schema:
                $ref: '#/components/schemas/IssueCreateMetadata'
          description: Returned if the request is successful.
        '401':
          description: Returned if the authentication credentials are incorrect or missing.
      security:
      - basicAuth: []
      - OAuth2:
        - read:jira-work
      - {}
      summary: Atlassian Get Create Issue Metadata
      tags:
      - Issues
      x-atlassian-data-security-policy:
      - app-access-rule-exempt: false
      x-atlassian-oauth2-scopes:
      - scheme: OAuth2
        scopes:
        - read:jira-work
        state: Current
      - scheme: OAuth2
        scopes:
        - read:issue-meta:jira
        - read:avatar:jira
        - read:field-configuration:jira
        state: Beta
      x-changes:
      - announced: '2023-12-11'
        details: https://developer.atlassian.com/cloud/jira/platform/changelog/#CHANGE-1304
        effective: '2024-06-03'
        type: removed
      x-atlassian-connect-scope: READ
  /rest/api/3/issue/createmeta/{projectIdOrKey}/issuetypes:
    get:
      deprecated: false
      description: Returns a page of issue type metadata for a specified project. Use the information to populate the requests in [ Create issue](#api-rest-api-3-issue-post) and [Create issues](#api-rest-api-3-issue-bulk-post).<br><br>This operation can be accessed anonymously.<br><br>**[Permissions](#permissions) required:** *Create issues* [project permission](https://confluence.atlassian.com/x/yodKLg) in the requested projects.
      operationId: atlassianGetcreateissuemetaissuetypes
      parameters:
      - description: The ID or key of the project.
        in: path
        name: projectIdOrKey
        required: true
        schema:
          type: string
      - description: The index of the first item to return in a page of results (page offset).
        in: query
        name: startAt
        schema:
          default: 0
          format: int32
          type: integer
    

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