PUT /rest/api/2/plans/plan/{planId}
Updates any of the following details of a plan using JSON Patch.
-
name
-
leadAccountId
-
scheduling
-
estimation with StoryPoints, Days or Hours as possible values
-
startDate
- type with DueDate, TargetStartDate, TargetEndDate or DateCustomField as possible values
- dateCustomFieldId
-
endDate
- type with DueDate, TargetStartDate, TargetEndDate or DateCustomField as possible values
- dateCustomFieldId
-
inferredDates with None, SprintDates or ReleaseDates as possible values
-
dependencies with Sequential or Concurrent as possible values
-
-
issueSources
- type with Board, Project or Filter as possible values
- value
-
exclusionRules
- numberOfDaysToShowCompletedIssues
- issueIds
- workStatusIds
- workStatusCategoryIds
- issueTypeIds
- releaseIds
-
crossProjectReleases
- name
- releaseIds
-
customFields
- customFieldId
- filter
-
permissions
-
type with View or Edit as possible values
-
holder
- type with Group or AccountId as possible values
- value
-
Permissions required: Administer Jira global permission.
Note that "add" operations do not respect array indexes in target locations. Call the "Get plan" endpoint to find out the order of array elements.
Servers
- https://your-domain.atlassian.net
Path parameters
Name | Type | Required | Description |
---|---|---|---|
planId |
Integer | Yes |
The ID of the plan. |
Query parameters
Name | Type | Required | Description |
---|---|---|---|
useGroupId |
Boolean | No |
Whether to accept group IDs instead of group names. Group names are deprecated. Default value: false |
How to start integrating
- Add HTTP Task to your workflow definition.
- Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
- Click Test request to test run your request to the API and see the API's response.