Backlog

Overview

The Backlog view is where you manage all upcoming work items in the project, including tickets and sprints. This view enables teams to prioritize and organize tasks before moving them into active sprints. From this page, you can manage tickets, create sprints, and track progress in preparation for upcoming work periods.

Accessing the Backlog view

To open the Backlog overview, go to the main side menu in Cloud Control Center, then select Project Management > Backlog.

Layout

The Backlog view displays collapsible tabs for both the backlog and any created sprints. The header of each collapsible tab contains the following elements:

• Sprint Name: The name of the sprint or "Backlog" if no sprint has been created.

• Sprint Duration: The length of the sprint, if applicable.

• Sprint Edit Icon: An icon that allows for editing sprint details (visible in sprint tabs).

• Number of Tickets: Displays the count of tickets in that tab, either in the backlog or a specific sprint.

• Status Badges: Color-coded badges indicating the count of tickets in various statuses:

  • Grey: Open tickets

  • Blue: Tickets in progress or under review

  • Green: Tickets marked as Done

  • Red: Blocked tickets (see Project Settings for enabling this status option)

  

Additionally, each collapsible tab includes the following action buttons:

• Backlog Tab: The "Create Ticket" button to create new tickets.

• Sprint Tabs: The "Start Sprint" or "Complete Sprint" button, depending on the current status of the sprint, allowing you to start or finalize the sprint's work period.

Ticket Management

Create New Ticket

To create a new ticket:

• Click the "Create Ticket" button located at the top-right corner of the collapsible Backlog tab.

• Once created, the ticket will automatically be added to the backlog or any selected sprint.

Search Tickets

You can search for tickets using the search bar and filters:

• The search and filter options are located at the top of the Backlog view.

• Search by ticket title, priority, status, or other relevant attributes to find specific tickets quickly.\

Sprint Management

Sprints in the backlog are used to organize tickets into work periods, allowing teams to focus on specific tasks for a set duration. You can manage the creation, activation, and completion of sprints from the Backlog view.

Create Sprint

To create a sprint:

• Click the "Create Sprint" button located at the top-right corner of the Backlog page.

• Enter the sprint details, including:

  • Sprint Name: The name will automatically increment based on the number of sprints already created. For example, "Sprint 1" will default to "Sprint 2" for the next sprint.

  • Sprint Length: Select from predefined options (1 week, 2 weeks, 3 weeks, or 4 weeks) or choose "Custom" to define your own duration.

  • Start Date and End Date: These are automatically set for predefined lengths. For custom lengths, you can select both dates using the calendar button.

• After setting the sprint details, assign tickets from the backlog to the sprint to organize tasks within the specified timeframe.

Edit Sprint

To edit a sprint:

• Click the Edit icon next to the sprint duration in the header of any sprint collapsible tab.

• Modify the sprint name or duration as needed.

• Save changes

Start Sprint

To start a sprint:

• Click the Start Sprint button displayed in the sprint header of any sprint collapsible tab.

• This moves the sprint from the backlog to an active state, indicating the team is starting work on it.

• Once the sprint starts, it will appear in the "Active Sprints" view, where it can be tracked and managed until completion.

Complete Sprint

To complete a sprint:

• Click the Complete Sprint button displayed in the sprint header of any sprint collapsible tab.

• This marks the sprint as completed, removes it from the backlog, and moves it to a completed state.

Move Tickets to Sprint

To move tickets from the backlog to a sprint or between sprints:

• Drag and drop tickets from the backlog section into the sprint section.

• Alternatively, use the "Move To" option from the ticket's context menu