Server to Cloud migration

[mike shoukry]

HI

I am trying to migrate from JIRA ON-PREM to JIRA CLoud, but running into issues with a custom ‘locked’ field migrating over.  

is the error due to the fact that the custom field is locked?  i cant even unlock it.  

what is the work around?

here is the error i get:

2023-09-29 23:54:59.936358 ERROR LOOP project-export The workflow: [PTS Customer Issue Workflow] transition: [In Progress] has unsupported custom field reference in config fieldKey for workflow rule validator [FieldRequiredValidator]. [JCMA 134] Double-check the workflow rule for missing config values or references.

[Trudy Claspill]

Hello @mike shoukry 

You need to look at the "In Progress" transition in the workflow named "PTS Customer Issue Workflow". The message is indicating that the is a Field Required Validator that is having a problem.

What is the configuration of that Validator?

[mike shoukry]

validator is:

If a value is not provided during the transition for field(s) Account, show the following error:An account is required to update this issue.. 

Account is a Locked field. custom field.  

[mike shoukry]

@Trudy Claspill 

[Trudy Claspill]

Are you migrated from Server or DC, and what version?

Are you using JCMA? If so, what version?

What is the field type for the Account field? It may be a type of field that is not supported by JCMA.

I don't have an Account field as either a custom or system field in my Jira Software/Service Desk, so it would seem that it is not a built-in field for the product. If you look at the field information does it give you any clue in the field description where that field may have come from?

If it is an unsupported field type, I would recommend removing the validator from the workflow and then trying to add it back in on Cloud after the migration.

[Trudy Claspill]

Types of custom fields that are supported by JCMA are detailed in this page:

https://support.atlassian.com/migration/docs/what-gets-migrated-with-the-jira-cloud-migration-assistant/

If the field type is one that is supported, there may be another reason it is not getting migrated. Check this article:

https://confluence.atlassian.com/cloudkb/jcma-doesn-t-migrate-supported-custom-fields-1129690600.html

[mike shoukry]

i think i found the ‘account custom field.

check this out:

https://tempo-io.atlassian.net/wiki/spaces/THC/pages/332201988/To+make+the+Tempo+Account+custom+field+required+in+Jira+field+configurations+in+Tempo+Timesheets+for+Server

you  think this wont ‘transfer/migrate’ over? @Trudy Claspill 

[Trudy Claspill]

What is the field type for Account? Not all field types are supported.

You should also check the Migration documentation from Tempo. The Marketplace listing should have a link under the heading Cloud Migration Support, if they offer some sort of cloud migration support.

Types of custom fields that are supported by JCMA are detailed in this page:

https://support.atlassian.com/migration/docs/what-gets-migrated-with-the-jira-cloud-migration-assistant/

If the field type is one that is supported, there may be another reason it is not getting migrated. Check this article:

https://confluence.atlassian.com/cloudkb/jcma-doesn-t-migrate-supported-custom-fields-1129690600.html

[Mark Ahnell]

The "FieldRequiredValidator" is a Workflow "Validator" that was part of some custom apps in Jira Server and Jira Data Center (Jira Misc Workflow Extensions and JSU Automation Suite are two of them I know of for example). The "Field Validator" Validator comes with Jira Cloud automatically, so for the "Cloud" versions of these Apps, they removed that Validator.

Solution:

1. Open the Workflow and take note of:
   1. The Workflow and Transition where the current "FieldRequiredValidator" Validator is
   2. What Field its validating
   3. Any custom message that's part of the Validator
2. Remove the Validator
3. Save the Workflow
4. After migration to Cloud, recreate this Validator using the native "Field Required" Validator in Jira Cloud.