Skip to end of banner
Go to start of banner

WIP: Unable to perform deployment: Unable to apply change 'type: change, old value: , new valueJiraConfigurationRoot#root/JiraFilter<Filter Name>_<user>, feature: columnLayout'

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Current »

\uD83E\uDD14 Problem

When performing snapshot deployment using the Configuration Manager for Jira app, the below error occurs :

“Unable to perform deployment: Unable to apply change 'type: change, old value: , new valueJiraConfigurationRoot#root/JiraFilter<Filter Name>_<user>/JiraColumnLayout# <Customfields present in coloumnlayout of the filter>, feature: columnLayout' “

The error indicates that there is more than one custom field with the same name in the column layout of a filter that the user is trying to migrate.

Example Error :

\uD83C\uDF31 Solution

  1. Analyze the Atlassian Jira logs and find which custom field is causing the error as in the below example:

Caused by: java.lang.IllegalStateException: More than one match is found for Custom field '<customfield name>'.

2. Remove the duplicate custom fields from the column of the filter.

In the below sample screenshot, you can see multiple ‘RCA Class’ fields present in the column layout of the filter. Remove the duplicate ‘RCA Class’ fields from the filter column layout.

3. Create a new snapshot and deploy.

4. If there are a large number of filters having the same set of duplicate custom fields in their column layouts, you can find all those filters by running the below SQL.

select cl.id, cl.username, cl.searchrequest, sr.filtername, cli.fieldidentifier
from columnlayoutitem cli, columnlayout cl, searchrequest sr
where cli.columnlayout = cl.id
and sr.id = cl.searchrequest
and cli.fieldidentifier IN ('customfield_xxxxx', 'customfield_xxxxx', 'customfield_xxxxx')
order by cl.id, cl.searchrequest

Note: In the 5th line of the SQL query, you need to mention the duplicate custom field IDs along with the original custom field ID.

  • Run the SQL above and save the results as CSV.

  • Filter all custom fields differently from the original custom field.

  • In Jira, open each filter and remove the columns with duplicate custom field names.

  • Recreate the snapshot and deploy.

  • No labels