I went in an added a new Story Points custom field and tied it to a new Story issue type, added that to a new Agile Issue Type Scheme, and tied that ITS to the project in which I was testing the Scrum board. I can now add story point estimates to the project.
Maybe I could rename the User Story issue type to Story for the same result, since the User Story issue already has a Story Points custom field.
As an extra datapoint, I noticed that we have two "Story Points" custom fields defined. One is assigned to all (Global) issue types and it used in many, but not all projects. The other is assigned to the "Epic" and "User Story" issue types and is used in one, defunct project. Might this be the problem or at least a contributing factor?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The RapidBoard "Plan" view allows you to enter an estimate on each issue. This populates the "Story Points" field and is displayed on each issue on the "Plan" view.
Once you begin a Sprint, you can update the estimate by simply editing the issue and changing the "Story Points".
Watch Atlassian's Greenhopper 6.1 video for a nice demonstration of estimating in points: http://www.atlassian.com/software/greenhopper/overview (0:56 shows estimating)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for taking time to help here, Anson. When we go to the Plan view, there's still no place to put the story points in. When comparing the production Jira system (where I think the problem lies) and the parallel test install of Jira/GH, the story point field doesn't show up anywhere in the production Jira system, yet we do see it in the parallel install.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.