1. Home
  2. Manage the projects
  3. Manage sprint Milestones in Jira projects

Manage sprint Milestones in Jira projects

Sprints date definition

In Jira you are only able to define the start and end date of the current sprint. To overcome this limitation Epicflow is able to calculate the future sprint dates based on user setting in the project info card or in the import menu. When you create a new future sprint in Jira and add tasks to it, then Epicflow will predict dates of these future sprints and show load accordingly.

Settings in the project info card are applied to all projects that use the same sprints as this project. In our example, we start the sprint on a Monday and it ends on a Friday, which is 12 days.

Screen #1– Sprint’s date in project’s card

Settings in the import menu are applied to all new projects and to all existing projects that are not adapted manually.


You can also select how many teams you run in parallel in a project. We start by explaining the setting for single teams and will continue with parallel teams.

Differences for single and parallel teams

For the single team

In this example we used the settings as defined in the section above; the sprint starts on a Monday, end 12 days later on a Friday.
The first milestone after today is the end of the sprint 33 dates as defined in Jira. The second MS is the start of sprint 34, which is starting on the next working day, etc.

Screen #2- Dates for teams

For the parallel teams

In case there are several teams working on one project but in different sprints, future sprint dates prediction in Epicflow can be performed in accordance with it. You can define that in section “Max parallel sprints” while importing.

Viewing sprint dates

The sprint dates are only depicted when there are tasks scheduled for that project. 

In case of no tasks scheduled for the particular Sprint it will be displayed as an empty one in the “Pipeline”. At the same moment if one sprint will contain different projects, for each such project you’ll have that milestone defined and aligned accordingly.

Also there is functional logic for the Start MS to pass child MS range visualization.
In case if there are no work hours between the two MS such range will be displayed in light blue with indication of not planned period or, as an example, period between two sprints.

Screen #3- Sprint Dates

Manual sprint date transfer in the pipeline

If at least one future sprint date was moved manually in the pipeline, all future sprint dates for the project (and projects, which share the same sprints) would not be re-calculated. Therefore, future sprints will be set according to the initial user setting in the project info card.

Starting a new sprint

On new sprint start the dates specified in Jira will be uploaded as the actual dates of the sprint, not that dates that were planned in Epicflow preliminary. It will be synchronized automatically.

Changing sprint date

Changing new sprint date when all future dates were automatically calculated will call for another  automatic recalculation of the all dates as well. 

Adding future sprint

Once the future sprint is added in Jira it will be automatically added to Epicflow.

Start backlog date

Start backlog date is defined as the next day after finish the last defined sprint date for the project. Note that the start backlog can differ per project.

Starting backlog date and sprints in Jira

If sprint is added/changed the start backlog date will change so it will be started after the last sprint date.

Sprints dates and future load

Epicflow represents the future load so you can predict bottlenecks and avoid overloading that causes delay ahead.

Sharing the same sprint for the different projects 

If several projects share the same sprint after page refresh all the dates will be aligned so start and end dates will be the same for that projects.

Updated on December 28, 2018

Was this article helpful?

Related Articles

Leave a Comment