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
Hello,
One of my team recently used a physical Kanban board and now I'd like to upload the work into Jira.
In the upload, I am having a hard time reflecting the status changes and cycle time.
Any guidance on what fields I need to use?
That one is a bit tricky. Essentially you need to use import issue history, which can really only be done by importing via a JSON data structure - https://confluence.atlassian.com/adminjiraserver071/importing-data-from-json-802592907.html
This user answered a similar question here - https://community.atlassian.com/t5/Jira-Software-questions/Can-we-import-history-to-jira-from-CSV/qaq-p/1837726
Hope that helps.
Kris
@Kristopher Perez that does help and hurt at the same time!
If I use the JSON format, is it possible to callout the status transition along the way, ie Develop Underway -> Develop Pullable -> Test Underway -> Test Pullable
Sounds like I'll be buying one of my developers lunch...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes - you'd have to, and you'd have to assign dates and an author for each item. The linked answer I gave shows how to do it perfectly.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
When uploading work from a physical Kanban board to Jira, there are several fields that you can use to reflect the status changes and cycle time. Here are some fields to consider:
When uploading work from a physical Kanban board to Jira, you may need to experiment with different field mappings and customizations to find the best approach for your team's workflow.
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.