How to migrate Jira Issue Field (Connect) to Jira custom field (Forge) in private app

Forge Adopting Forge from Connect
1

Hello,

I’ve a private custom addon that uses what before (in Connect) was called Jira Issue Field, and now I’ve to migrate to Forge using Jira Custom Field. The problem is that I want to preserve the same ID to not break all the JQL queries and not need to bullk the data from the “old” issue field to the “new” custom field.

Some help?

thank you !

2

Hi @OriolGarcia! Atlassian provides a built-in migration path that preserves the custom field ID (e.g., customfield_10054) so your JQL queries continue to work and you don’t need to manually bulk-migrate data.

You can find all the details related to the migration, along with the support forge custom fields types here - https://developer.atlassian.com/platform/adopting-forge-from-connect/migrate-jira-issue-fields.

Hope this helps, thanks :slight_smile:

3

Hi @RadhikaPatodiya,

Thankyou!

I’ve read it and I’m following the steps carefully because I don’t have my old connect addon installed on my dev environment and I cannot install it anymore due Atlassian remove the functionality.

So let’s play on prod :zany_face: