The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Jira Assets - Can't import new objects

Ryan Bollweg
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
October 9, 2023

Hi All,

I am attempting to create a number of new objects via the import function under an existing object type on JSM cloud. However when I attempt the import, I am given the following error message:

 

150 error(s) found in source data
  • Error: At least one value must be set. [Object (Label: 1, Id: Unknown)].
  • Error: At least one value must be set. [Object (Label: 2, Id: Unknown)].

This continues for the other 148 entries.

The data import sets a couple of fields, with "Name" being the identifier and label. Id is not a field configured in the object attributes or source data, so I assume it is the system field ID (which is the numerical part of the key generated when a new item is created)

I have automation set up to rename the objects based on the key post creation, hence the non-descriptive label. This import in this exact configuration worked ~ 1 week ago, so I am not sure what changed.

Any tips I can try would be appreciated!

 

Thank you,

 

Ryan

1 answer

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

3 votes
Answer accepted
Ryan Bollweg
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
October 9, 2023

Welp, I figured it out almost immediately after posting. There was an attribute I was using on the object type that had a minimum cardinality of 1 that I did not specify in the source file. Changing the minimum cardinality to 0 (as that data is no longer required) fixed the problem, as I imagine adding the data to the source file would have.

DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events