DC2C migration - columns saved with filters not migrated

Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
February 19, 2024

Hello folks,

I have executed a DC to Cloud migration for Jira Software DC v9.10.1 using JCMA 1.9.17.

Some of the saved filters that were migrated included saved Columns for the List view.

I have found that when I view those migrated filters in Jira Cloud in List view, the columns that display are the ones specified in My Defaults. If I click on Columns > Filter, it doesn't even show that the columns specified with the filter in Jira DC have been retained.

Has anybody else seen this behaviour?

3 answers

0 votes
Ting _Chiou Ting Teh_
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
September 12, 2024

This is indeed an expected behaviour as the saved columns are stored in a different database table and I don't think that table is being included during the migration.

 

I also found a feature request for this. Please upvote it if you would like to get it implemented for future version.

MIG-1296 - Filter migration with JCMA doesn't support column layout. 

0 votes
BG Pantaleon
Contributor
March 27, 2024

Hello,

 

Same issue here. The private filters' column setting from onprem didn't get migrated. Is this expected? Do we have an existing bug opened for this?

 

Thanks.

0 votes
Walter Buggenhout
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
February 19, 2024

Hi @Trudy Claspill,

Although I have done quite a few migrations to cloud, I must say I haven't paid attention to columns in the past. It has been the case that many filters (if they were cross-project) didn't even migrate at all in the past, so we were usually happy in many cases with the filters themselves just being there after a migration. 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events