Issue fields are organization-level or user-level fields that provide consistent, typed metadata across repositories owned by that organization or user. Unlike project custom fields, issue fields are defined once at the organization or user level and are available on issues owned by that organization or user and in projects owned by that organization or user. For more information on creating and managing issue fields, see Managing issue fields.
Issue fields in public and internal projects
Only fields with Public visibility appear in public and internal projects. Restricted fields are hidden. For details on configuring field visibility and how visibility changes affect projects, see Managing issue fields.
Adding an issue field to a project
To display issue field values in a project:
- Open a project and select a view using the table layout.
- Click in the table header.
- Click Add field.
- Select one or more issue fields from the list of available fields.
- Click Add.
The issue field appears as a column in the table view.
Removing an issue field from a project
To remove an issue field from a project:
- Click in the top right corner of the project page.
- Click Settings.
- In the left sidebar, select the issue field you want to remove.
- Click Remove field.
Removing an issue field from a project does not delete the field or its values. The field can be re-added at any time.
Editing issue field values in a project
You can edit issue field values directly in the project table view without opening the issue. Click on a cell in the issue field column to set or change the value. Changes are synced back to the issue automatically.
Grouping, filtering, and sorting
You can group, filter, and sort project views by issue field values, just like any other project field. This works in both table and board layouts.
You can also use issue fields to group by column on the board layout.
Charts and insights
Issue fields are available as data sources in project charts. You can create charts that group or segment by issue field values to visualize trends.
Limits
Projects support up to 50 fields in total. Issue fields and system fields count toward this limit. If a project is already at the field limit, you need to remove existing fields before issue fields can be added.
Note
Issue fields only apply to issues owned by the same organization or user. If a project contains pull requests, draft issues, or issues from another organization or user, issue field columns show empty cells for those items.