POST /orgs/{org}/issue-fields

Creates a new issue field for an organization.

You can find out more about issue fields in Managing issue fields in an organization.

To use this endpoint, the authenticated user must be an administrator for the organization. OAuth app tokens and personal access tokens (classic) need the admin:org scope to use this endpoint.

Servers

https://api.github.com

Path parameters

Name	Type	Required	Description
`org`	String	Yes	The organization name. The name is not case sensitive.

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
`visibility`	String	No	The visibility of the issue field. Can be `organization_members_only` (visible only within the organization) or `all` (visible to all users who can see issues). Only used when the visibility settings feature is enabled. Defaults to `organization_members_only`. Valid values: `"organization_members_only"` `"all"`
`name`	String	Yes	Name of the issue field.
`data_type`	String	Yes	The data type of the issue field. Valid values: `"date"` `"text"` `"number"` `"single_select"`
`description`	String	No	Description of the issue field.
`options[]`	Array	No	Options for single select fields. Required when data_type is 'single_select'.
`options[].priority`	Integer	Yes	Priority of the option for ordering.
`options[].name`	String	Yes	Name of the option.
`options[].description`	String	No	Description of the option.
`options[].color`	String	Yes	Color for the option. Valid values: `"yellow"` `"red"` `"purple"` `"gray"` `"blue"` `"pink"` `"orange"` `"green"`

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.