Move a team from Jira

Move one team at a time. Each import brings one Jira project into one Zentrik team, and the team’s velocity, cycle time and throughput start from its real Jira dates.

1. Connect Jira from Settings → Integrations → Jira. See Zentrik + Jira.
2. Match your people: open Settings → Members → Sync with integrations and choose Jira, so everyone’s work keeps its assignee. Work assigned to someone not matched arrives unassigned, and their comments keep their Jira name.
3. Choose the team. To keep Jira’s issue numbers, open the team’s menu, choose Edit team, set Task key to the project’s key, and import before the team has tasks.

1. Open Settings → Teams, choose the team, and pick Bring work from Jira… from its menu.
2. Find the Jira project and select it.
3. Choose All issues, or only the Open ones.
4. Read the review. It shows how many epics become initiatives, whether sprints become cycles, and whose work goes to which member. Use Match people for anyone not matched yet. If your plan has no room for more active initiatives, the review says which open epics arrive as tasks.
5. Point each Jira status at one of the team’s statuses. A status the team doesn’t have yet is added under Jira’s name.
6. Select Import N issues. The import runs in the background, so you can close the dialog.

• Issues become the team’s own tasks, with their descriptions, statuses, assignees, priorities, due dates, story points, labels, sub-tasks, links, comments, files and the full history of how they moved, dated as in Jira.
• Epics become initiatives, with their stories filed under them. An epic already linked to an initiative files its work there.
• Sprints become the team’s cycles. Closed sprints arrive completed, future ones planned, and the active one running. Unfinished work from closed sprints waits in the backlog, as it does on Jira’s board.
• Components and fix versions become labels. A version number such as 2.4 reads “Release 2.4”.
• Other Jira fields you filled in stay on each task under Provenance, read-only, beside the link to the issue in Jira.
• Issue keys stay the same when the team’s key matches the project’s key and the team had no tasks. Otherwise tasks take the team’s numbers, and their Jira keys still open them, in links and in branch names.
• Won’t Do and Duplicate work arrives canceled, so it never counts as delivered.

Files up to 50 MB are copied into Zentrik; larger ones stay in Jira. No one is notified about the past.

The import only reads Jira and never changes your issues, so Jira stays exactly as it was.

Turn on Keep following Jira in the review, and Zentrik catches up each morning on its own. It brings new issues, comments, links and files, moves cycles forward as Jira closes sprints, and takes Jira’s edits to tasks your team hasn’t changed in Zentrik. Once your team changes a task here, the task is the team’s, and Jira’s later edits leave it alone. The review shows when Zentrik last checked, what came across and when it checks next. Following is part of plans that include scheduled imports.

To catch up straight away, run the import again from the same menu. It brings only what changed.

A team that keeps working in Jira can show its sprints in Zentrik instead. Turn on Settings → Integrations → Jira → Sprints as cycles and choose the team’s board. Zentrik refreshes the sprints every 15 minutes, and their tasks stay read-only here with a link to Jira. Each team uses one or the other: a team whose sprints sync from Jira or Linear can’t also take an import.

Teams that still build in Jira can take work from Zentrik. On an initiative’s Tasks, open More task actions and choose Sync to Jira…. On its Stories, choose Sync stories. Pick the Jira project, issue type and parent issue, then map the fields. Zentrik creates or updates the issues and keeps each one linked to its initiative.

• Releases. Fix versions arrive as labels; release dates and version planning stay in Jira.
• Levels above Epic. They arrive as initiatives of their own, side by side; the nesting between them stays in Jira.
• Okta sign-in. Sign-in through Okta isn’t available yet. Your team signs in with email and password or Google.