Release New Feature

Import PBIs from CSV in one go — from your spreadsheet to Lasimban in a 4-step wizard

Update released

Launching a new project or migrating off another tool, clicking through PBIs one at a time gets old fast. With this update, you can pour them in straight from the spreadsheet you've already been working in.

📥 CSV bulk import via a 4-step wizard

A new “Import” icon now sits in the top-right of the product backlog list. Click it and a wizard walks you through:

  1. Download template — a CSV with your project’s current statuses baked in, generated on the spot
  2. Edit — open it in Excel, Google Sheets, Numbers, whatever you prefer
  3. Upload — drag and drop the edited file
  4. Preview → Confirm — row-by-row error check, then bulk register

Up to 1,000 rows per request.

✅ Row-level partial success — one bad row doesn’t waste the rest

If row 39 is missing a priority and row 102 has a typo in the status name, the other rows still go in. Only the rejected rows show up on the result screen.

Fix them in your spreadsheet, upload again. No more “start over from scratch.”

🌐 Row-level errors in 4 languages

“Title is required,” “Exceeds 255 characters,” “That status name doesn’t exist in this project” — every row-level error renders in Japanese, English, Tagalog, or Vietnamese, depending on the viewer. Multi-national teams can each read their own.

🧭 Status names auto-resolve to your project

The status_name column accepts whatever you actually call your statuses — “To Do,” “In Progress,” “Done,” or your own custom names. Leading/trailing whitespace and case differences are absorbed automatically, so copy-pasted CSVs just work.

🔒 Safeguard against accidental bursts

There’s a built-in 60-second per-user throttle. If you accidentally fire the import button several times in a row, the server has your back.

🚚 Migrating from Jira, Trello, Asana, or GitHub Projects? Smoother than you’d expect

A CSV exported from Jira, Trello, Asana, GitHub Projects, or similar tools drops in directly — just line up the header names and column order. Your first day on a new project shouldn’t be spent hand-typing PBIs one by one.

A rough header mapping:

  • “Summary” / “Title” / “件名” column → name
  • “Description” column → content
  • “Priority” column → priority (numeric)
  • “Story Points” column → story_point (numeric)
  • “Status” column → status_name (matched against your project’s statuses)

Status names absorb leading/trailing whitespace and case differences, so you don’t have to micromanage formatting drift from the source tool (“To Do” vs “TO DO” vs “to do” all resolve cleanly).

📮 Contact us

If you have any questions or feedback, please don’t hesitate to reach out.

Back to News