Linking issues with catalog entries is a great chance to enrich issues with information. The Catalog Select (single) is a custom field provided by the app. It allows users to link an issue with a catalog entry in a simple and convenient way – like with the standard Select List field.
The Catalog Select (single) custom field is a field based on Select List (single) standard Jira filed with its options populated from a Catalog directory. The field provides an ability to select one catalog entry to an issue. However, using several fields of this type you can set up complex dependencies that mirror the catalog directories relationship.
Navigate to Jira Administration → Custom Fields. Create a custom field of Catalog Select (single) type and put it to the relevant screens. Check how to Add a custom field (Atlassian Documentation)
Select a source directory for the field options.
Navigate to the field configuration in the Actions menu and reach the settings by clicking on 'Edit: Choose a custom directory for a field'.
To set up a simple selection just select a source directory in Select from a directory setting. In the example above, the field will work as a select list with the Services directory as the source.
All new-created entries from the selected directory will be automatically added as the field options. However, if you created the field when there were already some entries in the directory, use the Import button to fetch them.
If your Catalog objects are linked within Catalog, you can set the fields to filter available options according to these links.
For example, we have 2 directories: Countries and Cities. While the list of countries is independent, each city in the Cities directory has such property as 'Country'. Our goal is to restrict the city selection within an issue according to a selected country.
Create a Country custom field of the Catalog Select type. Set Countries as a reference directory.
Create a City custom field of the Catalog Select type. Set Cities as a reference directory. Set the Country field as the parent issue field.
Displaying of the linked issues
Linked issues are not displayed automatically in the entries since it's not always necessary. For example, you use a Catalog directory as a simple list of references. You always can find issues linked to a particular Catalog entry via Issue Navigator.
However, sometimes it might be convenient to see the linked issues (or some of them) right within an entry.
Just add a Linked Issues attribute while setting up your directory. Set the additional filters if required. Following are several examples of displaying linked issues in Catalog.
Examples of use
Case 1. We have a Services directory and allow our Service Desk customers to select a service from the list of available ones. We'd like to know instantly how many unresolved issues there are for a particular service.
- Add a Catalog Select (single) custom field and put it on screens of the relevant project. Name it Service.
- Add a Linked Issues attribute to the Services directory and set the additional JQL-filter: resolution is EMPTY. Name it Open Service Requests.
Case 2. We have the list of Services and need to make them rated by employees. They should be able to select the best and the worst ones and we will count votes.
- Add a Catalog Select (single) custom field, set up a selection from the Services directory. Put it on screens of the relevant project and name it The Best Service.
- Add a Catalog Select (single) custom field, set up a selection from the Services directory. Put it on screens of the relevant project and name it The Worst Service.
- Add a Linked Issues attribute to the Services directory and specify Linked via field(s) = The Best Service. Name it Selected as the best.
- Add a Linked Issues attribute to the Services directory and specify Linked via field(s) = The Worst Service. Name it Selected as the worst.