How to correct discrepancies between Foxly metrics and Jira custom fields created from Foxly

If a Foxly metric has a custom field linked to it and is configured as required in Jira, then any update to the metric—adding, renaming, or deleting metric options (custom field options that were created before)—will cause a discrepancy.

If there is a discrepancy between a Foxly metric and Jira custom field, you will receive the following warning message when saving the prioritization template:

Open

Use the following steps to correct the discrepancy:

1. Make Foxly custom field not-required (optional) in Jira field configuration.

2. Go to Foxly and uncheck the checkbox for the metric to be stored in the custom field.

3. Save the template.

4. Go back to Foxly and select store in the custom field.

5. Save the template.

6. Add the field back to Jira.

7. Make the field required again in Jira field configuration.

Open