{"meta":{"title":"Adding and managing issue fields","intro":"You can set, edit, and clear issue field values on individual issues to capture structured metadata for your team.","product":"GitHub Issues","breadcrumbs":[{"href":"/en/issues","title":"GitHub Issues"},{"href":"/en/issues/tracking-your-work-with-issues","title":"Issues"},{"href":"/en/issues/tracking-your-work-with-issues/using-issues","title":"Using issues"},{"href":"/en/issues/tracking-your-work-with-issues/using-issues/adding-and-managing-issue-fields","title":"Using issue fields"}],"documentType":"article"},"body":"# Adding and managing issue fields\n\nYou can set, edit, and clear issue field values on individual issues to capture structured metadata for your team.\n\nIssue fields appear in the right-hand sidebar of issues, alongside system fields like assignees, labels, and type. You can set values when creating or editing an issue. When you select an issue type while creating an issue, any fields pinned to that type automatically appear in the sidebar.\n\n> \\[!NOTE]\n> Issue fields are currently available on issues only. Pull requests do not support issue fields.\n\n## Setting a field value\n\n1. Navigate to the issue you want to update.\n2. In the right sidebar, if the field you want is not already visible, click **Add field**.\n3. From the dropdown, select the field you want to add.\n4. Set the value:\n   * For **single-select** fields, choose an option from the dropdown.\n   * For **text** fields, type your value. URLs are automatically detected and displayed as links.\n   * For **number** fields, enter a numeric value.\n   * For **date** fields, use the date picker to select a date, or type the date directly.\n5. Changes are saved automatically.\n\n> \\[!NOTE]\n> Issue fields cannot currently be pre-filled via URL query parameters or set through issue templates. To set field values, use the issue sidebar, projects, the API, or GitHub Actions.\n\n## Editing a field value\n\n1. Navigate to the issue.\n2. In the right sidebar, click on the field value you want to change.\n3. Select a new value or type a new entry.\n4. Changes are saved automatically.\n\n## Clearing a field value\n\n1. Navigate to the issue.\n2. In the right sidebar, click on the field value.\n3. Clear the value:\n   * For **single-select** fields, click the currently selected option to deselect it.\n   * For **text** and **number** fields, delete all text in the input.\n   * For **date** fields, click the clear button in the date picker.\n4. After clearing, the field is removed from the sidebar. It can be re-added using the **Add field** button.\n\n## Pinned fields\n\nIf your organization administrator has pinned fields to specific issue types, those fields automatically appear in the sidebar and the issue creation modal when you create or view an issue of that type. You do not need to manually add pinned fields.\n\n## Viewing field changes in the timeline\n\nWhen a field value is changed, the update is recorded in the issue timeline. The timeline entry shows:\n\n* Which field was changed\n* The new value that was set\n* Who made the change\n* When the change was made\n\nTimeline events for fields set to \"Organization only\" visibility are hidden from users who are not organization members or collaborators.\n\n## Field visibility\n\nOrganization administrators can set each field's visibility to \"Organization only\" or \"Public\". This affects what you see:\n\n* If a field is set to **Organization only**, it is only visible to organization members and repository collaborators with at least read access. If you are not a member or collaborator, the field does not appear in the issue sidebar, timeline, or search suggestions.\n* If a field is set to **Public**, it is visible to anyone viewing the issue.\n\nFor more information about configuring visibility, see [Managing issue fields in your organization](/en/issues/tracking-your-work-with-issues/using-issues/managing-issue-fields-in-your-organization#setting-field-visibility).\n\n## Using issue fields in projects\n\nIssue fields can be added as columns in project views, where you can edit values, group, filter, sort, and build charts. For more information, see [About issue fields in projects](/en/issues/planning-and-tracking-with-projects/understanding-fields/about-issue-fields).\n\n## Searching by field values\n\nYou can filter and search for issues based on field values on both the issues dashboard and your repository's issues page. In the search bar, type `field.` followed by the field name and value. For example:\n\n* `field.priority:high` to find issues with priority set to \"high\"\n* `field.\"target date\":>=2026-03-01` to find issues with a target date on or after March 1, 2026\n* `field.priority:high,medium` to find issues with priority set to \"high\" or \"medium\"\n\nFor more information, see [Filtering and searching issues and pull requests](/en/issues/tracking-your-work-with-issues/using-issues/filtering-and-searching-issues-and-pull-requests).\n\n## Using issue fields with the API\n\nIssue fields have full REST and GraphQL API support. You can automate field management, set values programmatically, and integrate with external tools.\n\n* **Managing fields**: Create, update, and delete organization-level fields. See the [Organization issue fields REST API](/en/rest/orgs/issue-fields).\n* **Using fields**: Get, set, and clear field values on individual issues. See the [Issue field values REST API](/en/rest/issues/issue-field-values).\n* **GraphQL**: Issue field types and mutations are also available via GraphQL. See the [`IssueFields` union](/en/graphql/reference/issues#union-issuefields), [issue field objects](/en/graphql/reference/issues#object-issuefieldtext) (such as `IssueFieldText`, `IssueFieldSingleSelect`, `IssueFieldNumber`, and `IssueFieldDate`), and [mutations](/en/graphql/reference/issues#mutation-createissuefield) (such as `createIssueField`, `updateIssueField`, and `setIssueFieldValue`).\n\n## Automating with GitHub Actions\n\nIssue field changes trigger webhook events on the `issues` event. You can use these as workflow triggers:\n\n* `field_added`: fires when a field value is set or updated.\n* `field_removed`: fires when a field value is cleared.\n\nFor example, to run a workflow whenever a field value changes:\n\n```yaml\non:\n  issues:\n    types: [field_added, field_removed]\n```\n\nThe event payload includes the field name, type, value, and previous value. For more information, see [Events that trigger workflows](/en/actions/reference/workflows-and-actions/events-that-trigger-workflows#issues)."}