![]() ![]() ![]() Given that, Advanced Roadmaps will fill the missing date values based on the child issues' dates. In order to roll up dates, a parent issue must have at least one child issue with start and end dates assigned. Dates of child issues can only be rolled-up if the parent issue does not have an assigned start or end date and is not part of a sprint. Rolled-up dates will also respect the group and color settings of your plan.Īny explicitly set dates will override rolled-up dates. By default, Advanced Roadmaps rolls up target dates, but you ca n configure your plan to use custom dates or sprint dates. Roll-up dates are treated the same as manually-set dates in Advanced Roadmaps. The rolled-up estimate of a parent issue will reflect how much work is yet to be done, and will decrease as you log time to child issues. When issue estimates are rolled up from child issues to parents, values are rounded to one decimal place for story points, and two decimal places for hours and days. Issues that are filtered out won't be included. Your rollup values are effected based on filters applied to your plan. In Advanced Roadmaps, you can roll up the following values: ![]() These auto-estimated values will appear in the parent issue next to a roll-up arrow icon (shown below), and reflect any changes to child issues. For example, if you roll up the dates on a story with three scheduled subtasks, Advanced Roadmaps will set the values of the parent issue according to the earliest start date and latest end date of the child issues. Once you set values for child issues, you can tell Advanced Roadmaps to apply those values to parent issues as well. If you’re using an earlier version of Advanced Roadmaps, this process may be different or not available in your instance. To unlock the full planning capabilities for these teams in your plan, you first must add them using the Teams in Advanced Roadmaps tab.The ability to roll up values to parent issues was introduced in Advanced Roadmaps version 3.23. When an issue is assigned to a team that’s not part of your plan, it shows as an external team. This issue will re solve itself once a future sprint becomes an active one. To compensate for this inconsistency in planning, Advanced Roadmaps will automatically create an external sprint because the same sprint can’t have two different start and end dates. If either or both of these are true, and you use Group issues by team and Show capacity on the timeline to plan future sprints based on capacity and velocity, the common sprint will occur at different times in each team swimlane. One of the teams for which you’re planning future sprints has a different iteration length configured.One of your future sprints appears on another Scrum board.There are two main reasons you may see external sprints on your plan: Issues imported from projects and filters may comprise multiple sprint assignments which will show on your timeline as external sprints. To avoid creating external sprints, we recommend that you use boards as issue sources where possible as a board only covers one sprint. However, you can’t assign new issues in your plan to an external sprint. You can update the sprint values of the issues assigned to these external sprints. However, since sprint data is based on boards, Advanced Roadmaps will add the EXTERNAL lozenge to indicate that these sprints are not directly associated with the project and filter issue sources. If you use projects or filters as your issue sources, their sprint assignments will still show on your plan. This prevents sprints from overlapping on the timeline and applies whether your issues are scheduled manually or through sprint assignment. When a sprint is completed, it will appear as finished on the last day. However, if the new dates fall before or after the sprint, you’ll see a warning. When Advanced Roadmaps uses sprint dates, the start and end date columns in your plan will display an S lozenge.įrom here, you can then change an issue’s dates manually without changing its sprint assignment. Once configured by your administrator, you can tell Advanced Roadmaps to schedule issues to sprints provided the issues have a sprint and team assignment but no due dates. ![]()
0 Comments
Leave a Reply. |