You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like the Add Cycle dialog to by default set the start date to be the next available date where a cycle can start. In general this would be the last available cycle.
Additionally, I would like the end date to be the same period of days / weeks / months as the period from the last available cycle.
This would help create large number of "sprints" for projects and organize things quickly for PMs
Why should this be worked on?
Jira already pre-fills sprints with a sequential name and time window of the last available sprint.
The text was updated successfully, but these errors were encountered:
We've structured our sprint cycles with three teams in a sliding window manner, starting a new sprint each Wednesday, each lasting for three weeks. This setup, which Jira supports, allows us to maintain maximum of a one-week lead time for prioritizing our backlog (but results in multiple sprints running concurrently).
I was evaluating Plane as an alternative to Jira, but the lack of support for concurrent Cycle is currently a blocker for us.
Is there an existing issue for this?
Summary
I would like the
Add Cycle
dialog to by default set thestart date
to be the next available date where a cycle can start. In general this would be the last available cycle.Additionally, I would like the
end date
to be the same period of days / weeks / months as the period from the last available cycle.This would help create large number of "sprints" for projects and organize things quickly for PMs
Why should this be worked on?
Jira already pre-fills sprints with a sequential name and time window of the last available sprint.
The text was updated successfully, but these errors were encountered: