Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Project Configurator for data Center - Custom IDs are different between Source and Target Instance

Jira 8.13.0

Project Configurator 3.7


I did a full project export from my source Instance to my Test Instance.  We noticed the IDs on the custom fields are different between the source Instance and Test Instance.  Why would the IDs be different?



1 answer

0 votes
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Feb 22, 2021

The ids for fields (and all the other objects) are generated independently in separate systems.  Unless your test system is an exact copy of production where no-one has done any additional config, you won't see the same IDs for custom fields (or other objects) as the counters will immediately start to count independently on the two systems.

This shouldn't matter though, PC is fully aware of it and handles different field IDs fine.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events