Manage Releases and Sprints

What release management controls

Releases and sprints are the planning layer inside a project. They help teams group work by timeline and by delivery scope.

• Current and future releases inside a project
• Sprint planning under the active release
• Task grouping for delivery tracking and reporting
• Separate Sprints and Backlog pages for focused review
• Jira CSV import into the selected project

Where this work now happens

Curoxi separates release planning across a few focused surfaces instead of keeping everything inside one dashboard view.

Project admins still manage releases and sprints from Project Operations, while delivery teams can open dedicated Sprints and Backlog pages from the main navigation.

• Project Releases in Settings or Project Operations for release and sprint setup
• Sprints page for a sprint-only view tied to the selected project
• Backlog page for current sprint backlog and full project backlog
• Dashboard release board for a quick visual summary

Important rules

• Sprint dates should stay within the release timeline
• Only project admins should manage release settings
• Tasks can move across sprints when delivery priorities change
• The selected project controls which releases, sprints, and backlog you are working on

Importing Jira tasks

Project admins can import Jira CSV exports from the release area.

The import flow lets you upload the file, map each Jira column to the current task fields, and optionally create project custom fields for any unmapped columns before the background import job begins.

• Use Import Tasks From Jira inside Project Operations → Releases
• Map CSV columns to current task fields before import
• Optionally create project custom fields for unmapped Jira columns
• Leave the page after starting the import; the job continues in the background

What outcome it improves

• Better planning by timeline
• Cleaner sprint ownership
• More reliable delivery dashboards

Recommended release flow

• Create the release first, then add sprints under it
• Mark the current release clearly before assigning work
• Use the delivery board to keep sprint allocations current
• Use the dedicated Sprints and Backlog pages when you want a cleaner view than the dashboard board

Explore Curoxi

Browse the core pages that explain how Curoxi works, how pricing is structured, and how to start a workspace.