DELETE /rest/api/2/field/association
Unassociates a set of fields with a project and issue type context.
Fields will be unassociated with all projects/issue types that share the same field configuration which the provided project and issue types are using. This means that while the field will be unassociated with the provided project and issue types, it will also be unassociated with any other projects and issue types that share the same field configuration.
If a success response is returned it means that the field association has been removed in any applicable contexts where it was present.
Up to 50 fields and up to 100 projects and issue types can be unassociated in a single request. If more fields or projects are provided a 400 response will be returned.
Permissions required: Administer Jira global permission.
Servers
- https://your-domain.atlassian.net
Request headers
| Name | Type | Required | Description |
|---|---|---|---|
Content-Type |
String | Yes |
The media type of the request body.
Default value: "application/json" |
Request body fields
| Name | Type | Required | Description |
|---|---|---|---|
associationContexts[] |
Array | Yes |
Contexts to associate/unassociate the fields with. |
associationContexts[].identifier |
Object | No | |
associationContexts[].type |
String | Yes | |
fields[] |
Array | Yes |
Fields to associate/unassociate with projects. |
fields[].identifier |
Object | No | |
fields[].type |
String | Yes |
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.