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 Export errors custom field not found

Receiving this error on export:

did not find referred Custom field with key 11901

Only problem is that there is no Custom Field with that key.  I am presuming the the "key" mentioned in the error is the same as a the customfield_id value.  If so, there is no custom field with that id/key.  

If key refers to an option for a custom field, how do I find that?

1 answer

Hi @Ashvin Patel ! thanks for your question!

If you could send this enquiry to our Support Portal so we'll have a look at your situation ASAP :-) Helps us to give you faster responses and more detailed support!




Was there ever a resolution to this?

I have the same error. I have an evaluation copy, so I don't have a login to the Adaptavist Product Support portal. This is a deciding factor on whether or not we purchase the app again.

@Ken Lange This issue was resolved.  The problem was actually related to a post function referring to a Resolution value, not an actual Custom Field, which is what the error stated.  The Resolutions had been deleted/removed without the workflows being updated.

I'd check the resolutions and the workflows that should be mentioned in the error and you should find that the resolution being used in the workflow is no longer on the system.  It might be resolution that is the issue, but that was the problem for me.

Hope this helped.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events