Developer
News and Updates
Get Support
Sign in
Get Support
Sign in
DOCUMENTATION
Cloud
Data Center
Resources
Sign in
Sign in
DOCUMENTATION
Cloud
Data Center
Resources
Sign in
  • Announcement banner
  • App data policies
  • App migration
  • App properties
  • Application roles
  • Audit records
  • Avatars
  • Classification levels
  • Dashboards
  • Dynamic modules
  • Field schemes
  • Filter sharing
  • Filters
  • Group and user picker
  • Groups
  • Issue attachments
  • Issue bulk operations
  • Issue comment properties
  • Issue comments
  • Issue custom field associations
  • Issue custom field configuration (apps)
  • Issue custom field contexts
  • Issue custom field options
  • Issue custom field options (apps)
  • Issue custom field values (apps)
  • Issue field configurations
  • Issue fields
  • Issue navigator settings
  • Issue notification schemes
  • Issue panels
  • Issue priorities
  • Issue properties
  • Issue redaction
  • Issue resolutions
  • Issue security level
  • Issue security schemes
  • Issue type properties
  • Issue type schemes
  • Issue type screen schemes
  • Issue types
  • Issue votes
  • Issue watchers
  • Issue worklog properties
  • Issue worklogs
  • Issues
  • JQL
  • JQL functions (apps)
  • Jira expressions
  • Jira settings
  • Labels
  • License metrics
  • Migration of Connect modules to Forge
  • Myself
  • Permission schemes
  • Permissions
  • Plans
  • Priority schemes
  • Project avatars
  • Project categories
  • Project classification levels
  • Project components
  • Project email
  • Project features
  • Project key and name validation
  • Project permission schemes
  • Project properties
  • Project role actors
  • Project roles
  • Project templates
  • Project types
  • Project versions
  • Projects
  • Screen schemes
  • Screen tab fields
  • Screen tabs
  • Screens
  • Server info
  • Service Registry
  • Status
  • Tasks
  • Teams in plan
  • Time tracking
  • UI modifications (apps)
  • User properties
  • Users
  • Webhooks
  • Workflow scheme drafts
  • Workflow scheme project associations
  • Workflow schemes
  • Workflow status categories
  • Workflow statuses
  • Workflow transition rules
  • Workflows
  • Other operations
Cloud
Jira Cloud platform / Reference / REST API v3

Issue panels

Postman Collection
OpenAPI

This resource supports bulk pinning and unpinning of issue panels that are added by a Forge app. Only Jira administrators can use it.

POST

Bulk pin or unpin issue panel to projects

Bulk pin or unpin an issue panel (added by a Forge app) to or from multiple projects.

The operation runs asynchronously. The response includes a task ID - use the Get task endpoint to check progress.

Permissions required: Administer Jira global permission.

Data Security Policy: Exempt from app access rules
Scopes
manage:jira-project

Connect apps cannot access this REST resource.

Request

Request bodyapplication/json

Forge module ID and the list of projects with pin or unpin action.

moduleId

string

Required
projectList

array<ProjectPinAction>

Required

Responses

Accepted. Returns the task ID for polling progress.

application/json

ForgePanelProjectPinAsyncResponse
POST/rest/api/3/forge/panel/action/bulk/async
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 // This sample uses Atlassian Forge // https://developer.atlassian.com/platform/forge/ import { requestJira } from "@forge/bridge"; var bodyData = `{ "moduleId": "<string>", "projectList": [ { "action": "PIN", "projectIdOrKey": "<string>" } ] }`; const response = await requestJira(`/rest/api/3/forge/panel/action/bulk/async`, { method: 'POST', headers: { 'Accept': 'application/json', 'Content-Type': 'application/json' }, body: bodyData }); console.log(`Response: ${response.status} ${response.statusText}`); console.log(await response.json());
202Response
1 2 3 { "taskId": "<string>" }
POST

Get issue panel pin status for projects

Get the pin status of an issue panel (added by a Forge app) for multiple projects.

The operation is read-only and runs synchronously. Projects that do not exist, or that you do not have permission to access, are returned in the response with the panel reported as not pinned and the reason in the error field; the request itself still succeeds.

Permissions required: Administer Jira global permission.

Data Security Policy: Exempt from app access rules
Scopes
manage:jira-project

Connect apps cannot access this REST resource.

Request

Request bodyapplication/json

Forge module ID and the list of projects to check.

moduleId

string

Required
projectList

array<string>

Required

Responses

Returned if the request is successful.

application/json

ForgePanelProjectPinStatusResponse
POST/rest/api/3/forge/panel/action/bulk/status
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 // This sample uses Atlassian Forge // https://developer.atlassian.com/platform/forge/ import { requestJira } from "@forge/bridge"; var bodyData = `{ "moduleId": "<string>", "projectList": [ "<string>" ] }`; const response = await requestJira(`/rest/api/3/forge/panel/action/bulk/status`, { method: 'POST', headers: { 'Accept': 'application/json', 'Content-Type': 'application/json' }, body: bodyData }); console.log(`Response: ${response.status} ${response.statusText}`); console.log(await response.json());
200Response
1 2 3 4 5 6 7 8 9 10 11 { "moduleId": "<string>", "statuses": [ { "error": "<string>", "pinned": true, "pinnedAt": 74, "projectIdOrKey": "<string>" } ] }

Rate this page: