How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Jira Issue custom field options (apps) API

This resource represents custom issue field select list options created by a Connect app. See [Issue custom field options](#api-group-Issue-custom-field-options) to manipulate options created in Jira or using the REST API.A select list issue field is a type of [issue field](https://developer.atlassian.com/cloud/jira/platform/modules/issue-field/) that enables a user to select an option from a list. Use it to add, remove, and update the options of a select list issue field.

Jira Issue custom field options (apps) API is one of 132 APIs that Jira publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Issue Custom Field Options (Apps). The published artifact set on APIs.io includes an OpenAPI specification, API documentation, authentication docs, and an API reference.

This API exposes 8 operations across 5 paths, and defines 10 schemas. It is described by OpenAPI 3.2.0, at version 1001.0.0-SNAPSHOT-82b018affa468e58f284fbe4df33536469d757df.

Requests are made against a single base URL, https://your-domain.atlassian.net.

8 operations 5 paths 10 schemas 2 DELETE4 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1001.0.0-SNAPSHOT-82b018affa468e58f284fbe4df33536469d757df
Base URL
https://your-domain.atlassian.net/rest/api/2
Authentication
OAuth 2.0, HTTP Basic
License
Terms of Service
Resource Areas
1

Authentication & Security 2

Jira Issue custom field options (apps) API declares 2 security schemes for authenticating requests. It supports OAuth 2.0 (OAuth2) using the authorizationCode flow, exposing 186 scopes. It accepts HTTP basic authentication (basicAuth).

  • OAuth2 — OAuth2 scopes for Jira
  • basicAuth — You can access this resource via basic auth.

Paths & Operations 8

Across 5 paths, the API surfaces 8 operations — 2 DELETE, 4 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Issue Custom Field Options (Apps) 8

This resource represents custom issue field select list options created by a Connect app. See Issue custom field options to manipulate options created in Jira or using the REST AP…

GET
/rest/api/3/field/{fieldKey}/option
Get all issue field options
getAllIssueFieldOptions 3 params → 200400403
POST
/rest/api/3/field/{fieldKey}/option
Create issue field option
createIssueFieldOption 1 param body → 200400403404
GET
/rest/api/3/field/{fieldKey}/option/suggestions/edit
Get selectable issue field options
getSelectableIssueFieldOptions 4 params → 200401404
GET
/rest/api/3/field/{fieldKey}/option/suggestions/search
Get visible issue field options
getVisibleIssueFieldOptions 4 params → 200401404
DELETE
/rest/api/3/field/{fieldKey}/option/{optionId}
Delete issue field option
deleteIssueFieldOption 2 params → 204403404409
GET
/rest/api/3/field/{fieldKey}/option/{optionId}
Get issue field option
getIssueFieldOption 2 params → 200400403404
PUT
/rest/api/3/field/{fieldKey}/option/{optionId}
Update issue field option
updateIssueFieldOption 2 params body → 200400403404
DELETE
/rest/api/3/field/{fieldKey}/option/{optionId}/issue
Replace issue field option
replaceIssueFieldOption 6 params → 303400403404

Schemas 10

The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are TaskProgressBeanRemoveOptionFromIssuesResult (13 properties), PageBeanIssueFieldOption (7 properties), IssueFieldOption (4 properties), SimpleErrorCollection (3 properties). Each schema is shown below with its type and property counts.

TaskProgressBeanRemoveOptionFromIssuesResult
object
Details about a task.
13 properties 8 required
IssueFieldOptionConfiguration
object
Details of the projects the option is available in.
2 properties
IssueFieldOptionCreateBean
object
3 properties 1 required
PageBeanIssueFieldOption
object
A page of items.
7 properties
RemoveOptionFromIssuesResult
object
3 properties
IssueFieldOptionScopeBean
object
3 properties
IssueFieldOption
object
Details of the options for a select list issue field.
4 properties 2 required
ProjectScopeBean
object
2 properties
SimpleErrorCollection
object
3 properties
GlobalScopeBean
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

jira-issue-custom-field-options-apps-api-openapi.yml Raw ↑

Other APIs Jira publishes across the network.

Jira Cloud Platform REST API v2
Jira Service Management Operations REST API
Jira Align REST API
Jira Customer Service Management REST API
Jira Issue Comments API
Jira Issue Priorities API
Jira Issue Search API
Jira Issue Statuses API
Jira Issue Transitions API
Jira Issue Types API
Jira Issues API
Jira Projects API
Where this information came from

This is an independent, third-party profile of Jira Issue custom field options (apps) API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.