You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Hi all,
I am trying to import many new ideas into JPD with a CSV file. In JPD, I am using the "Delivery Progress" and "Delivery Status" fields. When importing, I just pasted the Epic issue-id like KEY-123 into the column of these fields, as that is also working for the "Link "Relates"' field in JPD.
However, during import, JPD doesn't accept KEY-123 format and expects a number (I guess?).
So, how am I able to import data from Jira Cloud into these two JPD fields with a CSV file?
Thanks!
Hi @Mart Postma the delivery progress and status fields can't be imported as they are calculated fields based on the linked issues. I haven't been able to find a guide to import linked issues unfortunately, sorry about that!
Hi @Rohan Swami
Thanks for your answer. How come that when I add them manually in JPD, I also use the KEY-123 from another project to link it to a delivery status, but not when I import the key? And it does work in a similar fashion for linked issues such as "Relates" when I import the key with a CSV file.
I understand that for now there is nothing to change here, but just some feedback for development ;)
Thank you!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I believe it's because the logic here is that issues used for delivery progress calculations are a special type of issue link, we don't look at regular issue links to calculate delivery progress.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.