Observation with JSON import ..

{

"links": [

{

"destinationId" : "BUG-79",

"sourceId" : "BUG-78",

"name" : "clones"

}

]

}

This is sample JSON file what i am using to establish link of type "clones" between "BUG-78" & "BUG-79" via JSON import

Result of JSON import>

Link tpe is coming as "clones" for both source ID & destination ID ,

Where i was expecting for Destination it sould come as "is cloned by"

Note: if i do manually it comes correctly ..

Can any body please guide me ?

1 answer

Hey,

Can you confirm that the name of the Link type (as viewed in administration settings) is "Clones"? For example, the clone link type in our instance is called "Cloners" (with outward/inward descriptions of "clones" and "is cloned by"). :)

Yes, it is "clones" only & as u told outward/inward descriptions of "clones" and "is cloned by" for it..l

But via JSON import the link type is coming as "clones" for both Source ID & Destination ID , ..

Where as if i am using "Jelly script runner" it coming correctly so may be this is the limitation with JSON import ...

Suggest an answer

Log in or Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Posted Thursday in Off-topic

Friday Fun: Magic Eyes

...staring into the background. Once the image pops out in 3D, you can look around the picture and enjoy. If you will see if you are a true illusion master! :) You did it? :) Wow! Awesome! As a bonus...

423 views 79 11
Join discussion

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you