-
Suggestion
-
Resolution: Unresolved
-
29
-
12
-
We'd like to upgrade all of our projects from legacy projects to next-gen projects but there is one item giving us pause. Legacy projects have a wide array of reporting capabilities that we rely on. With the new next-gen projects, there are only two available reports, both of which require the use of sprints. We are a Kanban shop so we're not going to be using sprints. This means that if we transitioned to using next-gen projects then we'd have zero visibility into our velocity. Measuring our velocity is important to our team so we won't be able to upgrade until this oversight is addressed.
- is duplicated by
-
JRACLOUD-90119 Kanban reports in team-managed projects
- Closed
- is related to
-
JSWCLOUD-17708 Sprint report in Next-gen
- Closed
-
JRACLOUD-90474 Add user that closed the Sprint to the Sprint Burndown Report in Team managed projects
- Closed
-
JSWCLOUD-17914 Provide an epic report in Team-Managed scrum project
- Gathering Interest
- mentioned in
-
Page Failed to load
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
Yes, and...most of the filtering and report controls were removed for the team-managed projects, as compared to company-managed. This essentially makes things like the CFD useless for anything other than simple todo/in progress/done with no backflow or problems in delivery.
Who is the actual target audience for team-managed projects with such limited capabilities?