Note that this page only applies if you are using the
Classic Boards (which are no longer being actively developed;
read more).
If your project administrator has configured statistics (e.g. story points, time tracking), you can set statistical markers on your Planning Board to help you see how much work can be assigned to a particular version, component or assignee.
A typical scenario where you would use a statistical marker is:
- You have set up story points for your project. (A story point is just a custom statistic named "Story Point".)
- You have configured a maximum capacity of Story Point values for your versions.
- You want to assign issues from your backlog to a version based on issue ranking and your team's velocity (story point capacity per sprint).
Note that, if your project is using the 'Scrum' project template, the following custom statistics will have been configured by default: "Story Points", "Standard Issue Count", "Business Value" and "Time Remaining". However, you will only be able to use these if your administrator has configured them to show markers. Please refer to Configuring a Custom Statistic for details on how to show a statistical marker (note that only administrators can do this).
To use a statistical marker on your Planning Board,
- Log into JIRA or navigate to your dashboard, if you are already logged in.
Select Agile > Classic in the top navigation bar. Then select Classic Planning Board from the drop-down below the project name.
- Select your project from the project dropdown at the top left of the Planning Board, if it is not already selected. The Planning Board will refresh with information for your project.
- Display the issues for your selected version/component/assignee by clicking the header of the relevant box in the right column (e.g. click 'Unscheduled' to display the issues in your backlog).
You may also find it easier to view your issues as a list rather than as cards. - Use a context to sort your issues by the Rank field.
Note that the Rank field will only be available if your administrator has configured it for your project, as described in Configuring your General Project Settings. - Click the icon next to the desired statistic (e.g. 'Story Points', 'Time estimate'), in the box for the currently displayed version/component/assignee. The page will refresh and display a statistical marker (i.e. grey separator row) against your issues (see 'Statistical Marker Example' screenshot below). The statistical marker will have a number on the right of the separator row (editable by project administrators only) indicating the statistical value that you are grouping your issue by (e.g. 12 story points). The marker will be placed just above the first issue on the project board that will cause this statistical value to be exceeded.
Note that statistics will only be visible if your administrator has configured them to show markers, as described in Configuring a Custom Statistic.
Screenshot: Statistical Marker
1 Name of the statistic being used as a marker
2 Capacity — 'Max' value of statistic
3 Marker Value — Value currently being used to determine position of marker- If the Capacity and the Marker Value are not the same then an arrow appears between the two. Clicking the arrow will reset the Marker Value to the Capacity.
- If a 'texture' symbol appears in the middle of the bar, then you can:
- (project administrators only) To change the value of the statistic being grouped against, edit the value in the textbox on the right of the statistical marker row and press Enter (on your keyboard). You can also set the value to the capacity (i.e. max values specified when configuring the statistic for your Planning Board). The Planning Board will refresh and the statistical marker will be moved accordingly.
Screenshot: Statistical Marker Example
13 Comments
Martti Söderlund
hi,
should the standard issue count statistic have a meaning in a minor version (i.e. versions that have a Master attribute defined? I can't seem to get these to display correctly in GreenHopper 4.3.2.
br,
Martti
Nicholas Muldoon [Atlassian]
Hi Martti,
Yes, in a child version the marker for the standard issue count statistic is still applicable.
To display the marker for the standard issue count ensure that you have enabled the marker within the Statistics dialog.
Thank you Martti.
Regards,
Nicholas Muldoon
Anonymous
Can you add multiple markers using the same field with different values?
David Corley
Is it possible to associate different statistical marker settings per context?
EddieW
Created GHS-1201 - Getting issue details... STATUS to see similar function in the new rapid board scrum boards.
Anonymous
If a 'texture' symbol appears in the middle of the bar...
When does the 'texture' symbol appear or not appear? Some of our users are not able to move the markers as they don't see the texture symbol. Is moving the marker by dragging it only restricted to Administrators?
Tony Burke
Is there a way of setting up a permission so that only specific groups can change the marker value in the bar by either typing in a new value or moving the bar using the texture symbol. At the moment it looks like only administrators can change this but I want to allow other groups to change this value without making them administrators.
Regards,
Tony
Anonymous
Why do I not see 'Classic Planning Board' in my Agile menu? I am using ondemand version of Jira+Greenhopper. I am trying to figure out a way for capacity planning of my Agile Scrum project.
Rosie Jameson [Atlassian]
Can you please confirm that it is not visible under the Aglile > Classic menu?
Also, can I recommend that you try using the new board for your capacity planning?
Sean M
Are there plans to put statistical markers (or the ability to auto-create sprints based on a preset velocity) into the newer greenhopper board?
Tom Kotecki
Hi Sean,
It's definitely something on our radar, but I can't give you any timeframes at this point.
Cheers
Tom
ChuckBlingin
Can we search on those markers?
Rosie Jameson [Atlassian]
Not as such, sorry. One suggestion is to try out the sprints on the new boards, as sprints are searchable via JQL (currently, active and closed sprints are searchable; implementation of searching for future sprints is tracked here: GHS-5773 - Getting issue details... STATUS ).