Editorial
The Jira checklist that arrives without an owner
HeroCoders’ migration guide spells out what a ticket count won’t tell you: the checklist can make it to Jira Cloud without the people and deadlines that made it work.
Inês Valente1 min read

The Jira ticket made it to the cloud. So did the line that says ‘Check the rollback plan’. The person assigned to that line didn’t. If your migration report counts tickets, it has no reason to flag this one.
On 17 November, Dresden’s Elevatic announced an agreement to buy Poland’s HeroCoders, the maker of Checklists for Jira. The deal hasn’t closed. The buyer points to a deadline that has nothing to do with the deal: on 28 March 2029, Atlassian says Jira Data Center and its associated Marketplace apps go read-only when their licences expire.
I read HeroCoders’ guide to moving from Data Center to Checklists for Jira Enterprise. The app can import checklist items already applied to tickets, but it doesn’t migrate item assignees or due dates. The templates themselves have to be recreated. You could open an old release ticket and see its checklist, then create a new release ticket and find you can’t apply the same template.
I haven’t run that migration. But I wouldn’t sign one off from the import report. Give the team that actually ships a release one rehearsal in the new Jira. Can they start from the same checklist, and does everyone know which line is theirs before Friday? Let the import report tell you how many tickets moved. Don’t let it tell you whether the team is ready.
Monday digest
Europe’s best new software, every Monday.
Top launches, new listings and stories from the Journal. One email, skipped on quiet weeks.
Every product in the directory is checked before it goes live and shows where it’s made. Explore the directory

