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

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Insight object schema export from dev, import to production: external object reference fields fail

I have a development Jira site with three different Insight object schemas. Schema A has object attributes that are references to object in schemas B and C.

I exported and imported into production site the schemas B and C with no issues.  However, when I migrated schema A, with object references to the other two, the attribute fields to B and C were removed. 

The log file shows "Mismatch between object type attributes and headers in CSV file for object type ...."

The lost attributes are shown in the header list but not in the ObjectTypeAttributeBean list (example: ObjectTypeAttributeBean [id=109, name=Name, type=DEFAULT],). So the export from development was successful.

Object schemas B and C match on both systems, except B has a different key on each system. But C was stripped out too so I'm thinking that's not the cause.

Any suggestions for my next step? - Thanks

 

The headers in yellow are the reference fields to other schemas.

migrationLogError.JPG

1 answer

Did you ever solve this problem? 
I'm hitting it myself now. 

Schema A attribute refers to object in Schema B. 
Schema B is exported from source instance, exisiting Schema B dropped in new instance and then schema B imported in new instance. 

Schema A does not yet exist in new instance so it should just be imported, now that schema B is present and looks like the one on the other instance where both schemas A/B exists. 

Import fails to import Schema A after it's excported from source instance. 
It fails with the errors shown in this ticket. 
As well as some "Unable to store object type attribute ObjectTypeAttributeBean [id=null, name="""name of the refered to object attribute""" ...  just orior to the import zip file contents being analyzed according to the logfile.
and thne the message mentioned in this ticket: 
"Mismatch between object type attributes and headers in CSV file for object type ...."


How do I proceeed?
What did you do to solve? 

It hasn't been resolved as far as I know. Here's another thread that has a little more current information.

https://community.atlassian.com/t5/Atlassian-Cloud-Migration/Jira-Insight-object-schema-export-gt-gt-import-not-importing/qaq-p/1301971

 

I ended up recreating the schema and importing my assets via the mapping function. I cleaned things up a bit but it was certainly not the most efficient way to go about the migration.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira Service Management

Why upgrade to Jira Service Management Premium?

We often have questions from folks using Jira Service Management about the benefits to using Premium. Check out this video to learn how you can unlock even more value in our Premium plan.  &nb...

165 views 0 4
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you