Release in April 2025

This release focuses on making it easier to leave Checklists for Jira (by HeroCoders) behind and bring all of your existing data into Didit — including from the project type that used to trip migrations up.

What’s new and improved?

Migration Support for Team-Managed Projects NEW

Until this release, our migration tooling for users coming from Checklists for Jira (Free / Pro / Enterprise) only fully covered company-managed projects. Team-managed projects expose Jira fields differently, and the “Checklist Text (view-only)” field — the source of truth our converter reads from — needs to be explicitly added at the project level for team-managed projects.

We’ve now extended the migration documentation and converter to support team-managed projects end-to-end. The flow is:

• Project-level field setup: Open the project’s settings, go to Fields, and add the Checklist Text (view-only) field. Once it’s enabled, Didit’s migration tooling can read your existing checklists.
• Same migration paths as before: Once the field is in place, both individual checklist migration and global / bulk migration work in team-managed projects exactly the way they do in company-managed ones.

The full step-by-step guide lives at the top of the migration preparation page — look for the Team-managed projects section.

Migration Limitations Documented IMPROVED

We’ve also published an explicit table of how Checklists-for-Jira task statuses map to Didit task statuses (Open, In progress, Skipped, Done, and any custom statuses), so you know exactly what to expect before you flip the switch. Optional tasks, @-mentions, and task descriptions all have documented behavior on the migration page now.

If you’ve been holding off on migrating because of team-managed projects, this release removes the last big blocker. As always, our support team is happy to help with bulk migrations.