Jira

Jira Issue custom field contexts API

This resource represents issue custom field contexts. Use it to: * get, create, update, and delete custom field contexts. * get context to issue types and projects mappings. * get custom field contexts for projects and issue types. * assign custom field contexts to projects. * remove custom field contexts from projects. * add issue types to custom field contexts.

GitHub OpenAPI

Operations 14

Each operation below carries the questions people ask an LLM about it and the instructions they give an agent to run it. Generated by API Evangelist overlay

GET /rest/api/3/field/{fieldId}/context List the contexts of a custom field · Get custom field contexts #
Ask an LLM
“What contexts are defined for a custom field?”
“Can I list only the global context of a custom field?”
Tell an agent
List the contexts for custom field {fieldId}.
Show custom field {fieldId} contexts where global context is {isGlobalContext}.
POST /rest/api/3/field/{fieldId}/context Create a context for a custom field · Create custom field context #
Ask an LLM
“How do I create a new context for a custom field limited to certain projects?”
“What happens if I create a field context without any projects?”
Tell an agent
Create a context named {name} on custom field {fieldId}.
Add context {name} to field {fieldId} for projects {projectIds} and issue types {issueTypeIds}.
GET /rest/api/3/field/{fieldId}/context/defaultValue Get default values for a custom field's contexts · Get custom field contexts default values #
Ask an LLM
“What default value does each context of my custom field use?”
“Can I see the default for just one context of a field?”
Tell an agent
Get the context default values for custom field {fieldId}.
Show the default value of context {contextId} on field {fieldId}.
PUT /rest/api/3/field/{fieldId}/context/defaultValue Set default values for a custom field's contexts · Set custom field contexts default values #
Ask an LLM
“How do I set a default value for a custom field in a context?”
“Can I set defaults for date, option and user custom fields?”
Tell an agent
Set the context defaults for custom field {fieldId} to {defaultValues}.
Update the default values {defaultValues} across contexts of field {fieldId}.
GET /rest/api/3/field/{fieldId}/context/defaultValues Get a field's defaults grouped by context and issue type · Get default values for a custom field grouped by context and issue type #
Ask an LLM
“Can I see a custom field's default values broken down per issue type?”
“Which default applies to a given issue type within a field context?”
Tell an agent
List field {fieldId} default values grouped by context and issue type.
Show the per-issue-type default for issue type {issueTypeId} in context {contextId} of field {fieldId}.
GET /rest/api/3/field/{fieldId}/context/issuetypemapping List which issue types each field context covers · Get issue types for custom field context #
Ask an LLM
“Which issue types are mapped to each context of a custom field?”
“Can I check the issue type mappings for a single field context?”
Tell an agent
List the issue type mappings for contexts of field {fieldId}.
Show which issue types context {contextId} of field {fieldId} applies to.
POST /rest/api/3/field/{fieldId}/context/mapping Find which field context applies to project/issue type pairs · Get custom field contexts for projects and issue types #
Ask an LLM
“Which context of a custom field applies to a given project and issue type combination?”
“Can I look up the effective field context for several project and issue type pairs at once?”
Tell an agent
Find the context of field {fieldId} that applies to the project and issue type pairs {mappings}.
Look up which field {fieldId} context is in effect for {mappings}.
GET /rest/api/3/field/{fieldId}/context/projectmapping List which projects each field context covers · Get project mappings for custom field context #
Ask an LLM
“Which projects is each context of a custom field assigned to?”
“Can I see the project mappings for one specific field context?”
Tell an agent
List the project mappings for contexts of field {fieldId}.
Show which projects context {contextId} of field {fieldId} is assigned to.
DELETE /rest/api/3/field/{fieldId}/context/{contextId} Delete a custom field context · Delete custom field context #
Ask an LLM
“How do I delete a context from a custom field?”
“Can I still remove the global context of a field?”
Tell an agent destructive · confirm first
Delete context {contextId} from custom field {fieldId}.
Remove field {fieldId}'s context {contextId} entirely.
PUT /rest/api/3/field/{fieldId}/context/{contextId} Rename or redescribe a custom field context · Update custom field context #
Ask an LLM
“How do I rename an existing custom field context?”
“Can I change the description of a field context?”
Tell an agent
Rename context {contextId} on field {fieldId} to {name}.
Set the description of context {contextId} on field {fieldId} to {description}.
PUT /rest/api/3/field/{fieldId}/context/{contextId}/issuetype Add issue types to a custom field context · Add issue types to context #
Ask an LLM
“Can I extend a field context so it also covers more issue types?”
“What happens when I add issue types to a context that applied to all of them?”
Tell an agent
Add issue types {issueTypeIds} to context {contextId} of field {fieldId}.
Append {issueTypeIds} to the issue types covered by field {fieldId} context {contextId}.
POST /rest/api/3/field/{fieldId}/context/{contextId}/issuetype/remove Remove issue types from a custom field context · Remove issue types from context #
Ask an LLM
“How do I stop a field context from applying to certain issue types?”
“If I remove every issue type from a context, does it apply to all of them?”
Tell an agent
Remove issue types {issueTypeIds} from context {contextId} of field {fieldId}.
Take {issueTypeIds} out of field {fieldId} context {contextId}.
PUT /rest/api/3/field/{fieldId}/context/{contextId}/project Assign a custom field context to projects · Assign custom field context to projects #
Ask an LLM
“Can I assign a field context to additional projects?”
“Why does assigning a context fail if the project already uses another context of the field?”
Tell an agent
Assign context {contextId} of field {fieldId} to projects {projectIds}.
Make projects {projectIds} use field {fieldId} context {contextId}.
POST /rest/api/3/field/{fieldId}/context/{contextId}/project/remove Unassign a custom field context from projects · Remove custom field context from projects #
Ask an LLM
“How do I detach a field context from specific projects?”
“Does removing all projects from a context make it apply everywhere?”
Tell an agent
Remove context {contextId} of field {fieldId} from projects {projectIds}.
Unassign projects {projectIds} from field {fieldId} context {contextId}.

Documentation

📖
Documentation
https://developer.atlassian.com/cloud/jira/platform/rest/v3/intro/
📖
Authentication
https://developer.atlassian.com/cloud/jira/platform/rest/v3/intro/#authentication
📖
Documentation
https://developer.atlassian.com/cloud/jira/software/rest/intro/
📖
Documentation
https://developer.atlassian.com/cloud/jira/service-desk/rest/intro/
📖
APIReference
https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issues/

Specifications

⚙
OpenAPI
https://raw.githubusercontent.com/api-evangelist/jira/refs/heads/main/openapi/jira-issue-custom-field-contexts-api-openapi.yml

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API 
curl "https://apis.io/api/v1/apis/jira:jira-issue-custom-field-contexts-api"
All apis 
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

jira-issue-custom-field-contexts-api-openapi.yml Raw ↑ 
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: https://developer.atlassian.com/platform/marketplace/atlassian-developer-terms/
  title: Jira Cloud platform REST Issue custom field contexts API
  version: 1001.0.0-SNAPSHOT-82b018affa468e58f284fbe4df33536469d757df
servers:
- url: https://your-domain.atlassian.net
tags:


# --- truncated at 32 KB (108 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/jira/refs/heads/main/openapi/jira-issue-custom-field-contexts-api-openapi.yml