You can create different types of Custom Fields. These can be mainly categorized as “Standard Custom Field” and “System Value as Custom Field”.
Standard Custom Field
The following list describes these standard types and their use:
- Text Field – to enter simple text
- Drop Down – to provide list of multiple values to user, where only one can be selected at a time
- Check Box – gives a few options to user, where user can select one or more
- Multi Select Dropdown – to add and select multiple values.
- Radio Buttons – to add a few values and let User select only one
- URLs – lets users to add only URLs.
- Date Picker – lets user add only date
- Rich Text Field – allows user to enter a rich text
- Tags – to add tags or labels
Note: Consider following notes, while defining a multi-choice field like Drop Down, Checkbox, Multi Select Dropdown, or Radio Button Custom Field.
- Add options one by one – Use Add Option button to add each option in the list
- Reorder values – Drag and drop to reorder values in multichoice list
- Edit multi-select values after saving – you can add or remove values from the list by editing the field anytime
System Value as Custom Field
System Value as Custom Fields are designed to fetch current Project data from other fields. These fields are multi-select. Often there are needs by customer to use System fields like Sprints in different ways.
For example, if you want to capture “Issue Reported in Sprint”, then you can simply create a custom field of type Sprint. Sprint type custom field will have names and IDs of all the current and old sprints. Supported System Values are:
- Sprint – Sprint numbers are fetched and user can select multiple values
- Release – Release ids are fetched and user can select more than one value
- Epic – Epic ids are fetched and user can select more than one value
- User – User IDs are fetched and user can select multiple IDs
Example of “Release” as Custom Field
Problem: Default Release field in Issues can only have single value. So if the Issue is impacting multiple Releases, it is not possible to link single Issue to multiple Releases.
Solution: Define a “Release” Custom Field for Issues, where you can select multiple Releases. Follow this step by step guide to add Release as Custom Field.
- Select Custom field type as Release
- Define Field Details and if it will be a Required field
- Define Scope – by selecting available at “Issues”
- Mark Project name under “Visibility in projects”. Save the changes
- Open an Issue of the same project in Detailed view
- This newly created field can be found under Custom Field section at the very bottom of “Issue” details.
- Check that all Releases of the project are listed under this Release Custom Field. Users can select multiple values as well.