Skip to main content

Public

Project privacy set to public. By default, its content is available to everyone (authenticated or not). Please note that more restrictive permissions might exist on some items.

  •  
     
    story #10633 see velocity in agile dashboard
Actions
Summary
Empty
see velocity in agile dashboard
Empty

Update "Overview" tab (as of 9.17 release) that already contains backlog table, burn-up and burndown.

  • Display a bar chart with submilestones velocities under Burndown/Burnup charts (depends on story #10632 for the value)
  • Chart is rendered with D3.js
  • The bar chart is ordered by sprint (as of planning view), the x-axis displays sprint names and the dates are also available in the tooltip
  • The bar chart only render when
    • There are submilestones with "velocity" defined (in Tuleap Scrum template, velocity would be visible only in "Release" details tab)
    • At least one submilestone is Closed.
  • All submilestones are displayed with a given limit (7 submilestones) to be sure to be able to render graph

On the backend side

  • will be handled by hook mechanism
By Benjamin Dauton (bdauton_enalean)
(317 kB)
overview-velicoties-graph.png
Laurence Terrien (ltn)
Status
Empty
Done
Development
  • [ ] Does it involves User Interface? 
  • [ ] Are there any mockups?
  • [ ] Are permissions checked?
  • [ ] Does it need Javascript development?
  • [ ] Does it need a forge upgrade bucket?
  • [ ] Does it need to execute things in system events?
  • [ ] Does it impact project creation (templates)?
  • [ ] Is it exploratory?
Empty
Details
#10633
Manuel Vacelet (vaceletm)
2018-03-29 10:26
2017-09-08 11:20
4438

References
Artifact links
Empty
Referencing story #10633

Artifact Tracker v5

epic #10630 Scrum / Velocity
story #10673 see BurnUp chart in agile dashboard
rel #10994 9.19

Git commit

tuleap/tuleap/stable

Velocity of backlog items are displayed in overview tab 49e418f5d3
User avatar Marie Ange Garnier (marieange) , 2018-03-22 10:51
At release level, if sprint has no velocity semantic, an error should be displayed ce1a8f853d
User avatar Marie Ange Garnier (marieange) , 2018-03-22 15:18
Update scrum configuration 831c33fbcb
User avatar Marie Ange Garnier (marieange) , 2018-03-22 15:27
Extract beforeEvent in a dedicated object and add unit tests bd77261b89
User avatar Marie Ange Garnier (marieange) , 2018-03-23 14:07
Semantic velocity display choose field even if a field is set 780fa8bd3c
User avatar Marie Ange Garnier (marieange) , 2018-03-23 16:09
Duration and velocity can be Float values 640364fe43
User avatar Marie Ange Garnier (marieange) , 2018-03-26 09:44
Draw velocity chart ab700173b6
User avatar Thomas Gorka (tgorka) , 2018-03-26 08:59
Add tooltips on bar chart 0f0ffa1253
User avatar Thomas Gorka (tgorka) , 2018-03-26 12:08
Sprint without start date should be displayed as error in grpah 46301dd1c1
User avatar Marie Ange Garnier (marieange) , 2018-03-27 11:33
Truncate sprints names to prevent overlapping 63310f7561
User avatar Thomas Gorka (tgorka) , 2018-03-27 11:15
Prevent script to render the graph if no mount point c800e853b8
User avatar Thomas Gorka (tgorka) , 2018-03-27 17:29
Add missing vendor directory in velocity packaging 4985bba34a
User avatar Thomas Gerbet (tgerbet) , 2018-03-28 00:31
Graph should only display 7 artifacts 0599b4ffb4
User avatar Marie Ange Garnier (marieange) , 2018-03-28 10:29
Display settings

Follow-ups

User avatar
Thomas Gorka (tgorka)2018-03-23 14:12
last edited by: Thomas Gorka (tgorka) 2018-03-23 15:21
Display 15 sub-milestones is too much for the graph. 7 milestones is the very limit we can handle.
  • Acceptance criteria
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes
User avatar
Marie Ange Garnier (marieange)2018-03-21 10:13
  • Acceptance criteria
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes
User avatar
Thomas Gerbet (tgerbet)2018-03-05 10:56
  • Acceptance criteria
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes
User avatar
Benjamin Dauton (bdauton_enalean)2018-03-02 10:19
  • Acceptance criteria
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes
User avatar
Manuel Vacelet (vaceletm)2018-01-23 11:10
  • Acceptance criteria
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes
  • CC list set to Laurence Terrien (ltn)
User avatar
Manuel Vacelet (vaceletm)2017-09-25 15:44

@nynoe the left hand side is not OK.

With the new content, there should be only one table with both open & closed stories. Moreover it shouldn't be possible to add or remove anything from there. "Content" is really meant to be a read-only page that could be pointed out:

  • During Sprint/release to have a quick view of what's going on (thanks to the content + charts)
  • After the spring/Release to know what's in the release

 

User avatar
Marine Pieux (nynoe)2017-09-25 15:08
  • Acceptance criteria
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes
  • Attachments 1-scrum-release-tab-details@1x.png added
  • Permissions set to