# Feature AGILE-326 - Multiple active sprints without sharing

Project: Stream agile
Status: closed
URL: https://community.openproject.org/work_packages/AGILE-326

## Planning

| Attribute | Value |
| --- | --- |
| Date | 2026-07-24 |
| Priority | Medium |
| Target versions | 17.7.0 |
| Sprint | Sprint 6 |
| Backlog bucket |  |
| Votes |  |
| List |  |
| Roadmap |  |
| Relevance |  |

## OPEN POINTS / FEEDBACK

_No work packages_

## Features and Chunks

_No work packages_

## Bugs and other work packages

| ID | Type | Subject | Status | Assignee | Target versions | Spent time | Module |
| --- | --- | --- | --- | --- | --- | --- | --- |
| AGILE-349 | Bug | Multiple active sprints: address remaining open points | closed |  | 17.7.0 |  | Modules and project features / Backlogs |
| AGILE-353 | Code maintenance | Rename "SprintSharing" mixin | closed |  | 17.8.0 |  | Modules and project features / Backlogs |

## Technical Details

| Attribute | Value |
| --- | --- |
| Module | Modules and project features / Backlogs |
| Feature Flag |  |
| Requires doc change | Yes |
| Enterprise plan | Enterprise / Basic (BAS) |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups | https://www.figma.com/design/yRewu4Y5nuWCa8aMM3DFw3/Agile--Sprints-and-Backlogs?node-id=5307-152508&t=l8D9kkfQbqyW7i2n-4 |
| Accessibility | No |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Developers | OP Dev Polaris Team |
| Designer | Parimal Satyal |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| PD (min) |  |
| PD (max) |  |
| Work |  |
| Labor costs |  |

## Description

**As** an agile user  
**I want to** activate multiple sprints at the same time  
**so that** multiple teams can work within the same project at the same time

#### **Acceptance criteria**

  - **If configured for the project, multiple sprints can be activated at the same time.**
    
      - There is no limit to how many sprints can be activated
    
      - The functionality for activating sprints is unchanged, i.e. a board is created when activating and the status is changed.

  - Within the project administration of backlogs, a user can configure to have multiple active sprints in the project. 

  - **In project settings,**
    
      - ~~Rename "Backlogs" to "Backlog and sprints"~~ extracted into its own feature <mention class="mention" data-id="77222" data-type="work_package" data-text="#AGILE-332" data-display-id="AGILE-332">\#AGILE-332</mention> 
    
      - Add a new tab called "Multiple active sprints".
        
          - Leave "Sprint sharing" as is.
    
      - In the 'Multiple active sprints' tab, add a setting to enable/disable multiple active sprints.
        
          - There is a toggle ("Allow multiple active sprints").
        
          - These options will only be available when 'Don't share' is selected in the 'Sprint sharing' tab.
            
              - If any other option selected (i.e, the project is sharing is receiving sprints), the toggle switch is not visible. Instead, an [InlineMessage](https://primer.style/product/components/inline-message/#tone-variants) (scheme: unavailable) informs the user that multiple active sprints are not available when sprint sharing or receiving is enabled.
            
              - This message has a link to the Sprint sharing tab.
        
          - If multiple active sprints is enabled, the project no longer has the limitation of having just one sprint marked as active at any given time. It can have multiple sprints active in parallel.
    
      - Activating the setting disables the possibility to change the sharing settings in the 'Sprint sharing' tag.
        
          - The options will be replaced with an InlineMessage.
    
      - If there are currently multiple active sprints running, the setting cannot be changed.
        
          - There is an InlineMessage (scheme: warning) that informs users that they need to have only one (max) sprint currently active in order to go back to limiting the number of active sprints to one.
    
    <br>

**Technical notes**

<br>

  - 
    <br>

**Permissions and visibility considerations**

  - \[open\] permission necessary for configuring using multiple active sprints in the project - "Share sprint"?

**Translation considerations**

  - *Key terms and phrases in the key languages*

**Out of scope**

  - Sharing sprints and multiple active sprints active at the same time within the project

  - Reporting functionality that requires knowing the continuity of sprints,
    
      - e.g. all those belonging to "Team A" to calculate a velocity chart

  - Assigning a sprint to a team

  - Changes to the close sprint functionality