Optionalcontexts?: {List of contexts of the UI modification. The maximum number of contexts is 1000. If provided, replaces all existing contexts.
Optionaldata?: stringThe data of the UI modification. The maximum size of the data is 50000 characters.
Optionaldescription?: stringThe description of the UI modification. The maximum length is 255 characters.
Optionalname?: stringThe name of the UI modification. The maximum length is 255 characters.
The ID of the UI modification.
Optionaloptions: RequestOptions
Updates a UI modification. UI modification can only be updated by Forge apps.
Each UI modification can define up to 1000 contexts. The same context can be assigned to maximum 100 UI modifications.
Context types:
Jira contexts: For Jira view types, use
projectIdandissueTypeId. One field can act as a wildcard. Supported Jira views:GIC- Jira global issue createIssueView- Jira issue viewIssueTransition- Jira issue transitionJira Service Management contexts: For Jira Service Management view types, use
portalIdandrequestTypeId. Wildcards are not supported. Supported JSM views:JSMRequestCreate- Jira Service Management request create portal viewAgent view contexts: For Agent view types, use
projectIdandissueTypeIdlike Jira contexts, and optionally setrequestTypeId.portalIdmust not be set. One ofprojectId,issueTypeId, orviewTypecan act as a wildcard. Supported Agent views:GICAgentView- Agent view variant of Jira global issue createIssueViewAgentView- Agent view variant of Jira issue viewIssueTransitionAgentView- Agent view variant of Jira issue transitionPermissions required:
The new
write:app-data:jiraOAuth scope is 100% optional now, and not using it won't break your app. However, we recommend adding it to your app's scope list because we will eventually make it mandatory.