(8.1.1) Mapping project fields as jira custom fields

Custom fields are a very important part of the Jira core functionality. Using them, we are able to perform many extra actions.

It is possible to associate a project field with a Jira custom field for the following project field types:

Text field
Number field
Date field
Duration field
User field
Project field
Group field
List field
Status field
Priority field

is not possible to associate a project field with a Jira custom field on a cumulative issue field nor script field. The reason is that the nature of the mechanics of calculated fields may cause performance issues and slow Projectrak down.

Custom fields map project fields values

It is very important to remember that every associated Jira custom field will get its value from a project field. For this reason, to ensure you get the results you expect in your Jira workflow, both fields must be synchronized.

How to configure mapping

The process to associate a project field is really simple. On the fields page (Go to Projectrak → Fields), create a new project field or edit an existing one, and then select the custom field association option: Map into a Jira issue custom field.

IMPORTANT: Be aware that, as per the Jira permissions scheme, the field value will be visible to anyone who has access to the issue and the field.

Custom field details

When a field with mapping is saved, a custom field is created with the same name and description as the associated project field.

We recommend you edit and configure the context of the custom field.

Finally, it incorporates the field in the view screen (In this case AT RISK is the project status)