見積もりとトラッキングの設定

Hi,

The Rapid board is really simple to use but we have an issue with one thing. When configuring the field "Estimation Statistic" to "Original Time Estimate" we noticed the following:

•  When adding tasks with estimations (ex 4hrs) to Stories in the Plan board, the field "Estimate:" does not display the Total Estimate time of all Sub Tasks.
• When viewing the Story in Jira (outside the Rapid Plan Mode) the Time Tracking is displayed. It would be great to display this in the Rapid Board Plan Mode view.

Is there any configuration I need to set? 

I have the same problem.

What does it mean if I don't see the Estimate tab? I see Filter, Columns, Swimlanes, and Quick Filters, but that's it. Please advise. Thanks!

I have the same issue - I believe its permission related

Same issue as Mike. It's ignoring the original estimate, time spent, time remaining of the sub-tasks of the Story tickets in the Sprint. This renders the Rapid Board burndown chart useless for our team  as we use sub-tasks for the Sprint Backlog. This is not the only case of sub-tasks not being supported around the Rapid Board functions. Here's hoping they've just not got around to it yet.

Hey folks. This issue has been detailed in GHS-5283 - Getting issue details... STATUS

Add comments and vote to get the GreenHopper team to take notice!

It looks as though this is only available for a scrum board not a kanban board (no estimation tab). Is there any way to have this on kanban. We currently use the kanban board to do a lot of our scrum work as the scrum board is still way too immature to work with.

Hello, yes this would be such a nice feature. It's painful to keep track manually of the summed up time estimates of each sub-task in order to get an estimate for each story. Also, open access to the issue so we can vote on it would be lovely. thanks!!

Yeah I just signed up for greenhopper and noticed the same problem. Too bad it doesn't show the estimate for the task.

They should definitely change this!

Is there any option to use the Remaining Estimate instead of Original Estimate?

Use Case: a story with Original Estimate of 20h was not finished within a sprint (Remaining Estimate is 4h). While finishing the sprint the story is added to the top of the backlog and shown as 20h. For sure this has an impact on the Team commitment.

Is there any option to change this behavior? If there are subtasks existing then in ideal case it should show the aggregated Remaining Estimate. So it would be great to have an additional option of 'Remaining Estimate' in the 'Estimation Statistic' dropdown

I agree with Markus. I would like to use remaining estimate instead of original estimate in the planning mode.

Hi!

How can we track how much time was planned for a person in the sprint vs. the person's individual capacity? On the Classic Planning board I can at least create a statistic based on Remaining Work and set a max value. Then I can see the grey bar on the planning board that shows per person which work will fall off the plate. 

How can I do this with the new rapid board? There seems to be absolutely no ability to see how many hours were planned per person and how many hours are remaining in the sprint per person.... Or am I missing something?

Thanks!

Hi,

The documentation says "Alternatively, you can choose any numeric custom field on your JIRA system". How do you do that? None of my custom fields show up in the drop down.

Thanks for any help!

We need to have a way to have the burndown chart be based on total issues (tasks, sub-tasks) for the y-axis in the current sprint but also be able to enter an original estimate and remaining estimate on a per task basis.   Is there a way to do this??

Hi,

If i configure Estimation statistic = "Estimate time and Tracking"= "Remaining estimate and Time spent", i see only Issue Count, and Estimate summary in Sprint footer.

But in  example,  the footer of sprint contains also the sum of Remaining hours.

How can I get this shown be me?

I am currently using Greenhooper V.6.0.2

Thanks

Hi, When creating a Story with original estimate and then adding sub tasks to it, the sub tasks add to the remaining time but not the original estimate.

The way the estimate calculation is now it is impossible to create sub tasks to the story in sprint planning and finish them off in the sprint and have correct statistics. Either you have to set the original estimate of the story to 0 and so you get a faulty velocity but correct remaining time when finishing sprint or you set original estimate but you get faulty remaining estimate for story since it is calculated as sum of subtasks + original estimate.

Please fix this by allowing original estimate time of a story to be sum of its subtasks before the sprint begins. After the sprint begins, if a sub task is created then add its estimate to the remaining.

I have a question regarding the Time Tracking using "Remaining Estimate and Time Spent" - 

Do values burn down for stories only, or also for sub-tasks? (coming to think of it, the question is also relevant to using the "None" time tracking, in which burndown is based on original estimation).

Thanks.

Is it possible to display both the totals of Story Points and Original Estimate for a sprint in the Plan view?  We've estimated the story points and now the team wants to know the total number of hours estimated before making a commitment.  This is our first sprint, so we have no baseline on which to establish confidence of our velocity in Story Points. As a workaround, I can just change the board configuration to use Original Estimate–just wondered what others do.

It would be nice, if JIRA would consider sub-tasks if the estimation set to "issue count" (We have a limited number of user stories and a lot of sub-tasks)

I have just started using JIRA 5 (was JIRA 4 in last company) and want to track sub-tasks by time in a sprint. We go into the sprint with the points we believe that we can do in the sprint, but break them into tasks which are estimated in hours/days and assigned to team members. I could do this in version 4, but not version 5 it seems. Can anyone help me? I am considering the "custom field". Thanks!

Nicholas Muldoon [Atlassian], We have a situation where we need to change the estimate of an issue within the current sprint. E.g. We start off with say story points 4, but 3 days into sprint, we might find more details and find out htat we either need to bump it to 8 or down to 2 based on the level of work. Any idea how to make that field "editable" in the current sprint. Currently the only way I can do it is (a) remove it from sprint (B) change the estimate and (c) add it back in sprint. That is non-intuitive. Shouldnt this be reflecting reality whereby in many cases we go with an estimate, and need to change it based on the level of work required. 

I am the administrator. Can this be editable by any team member for their current tasks in a sprint? 

Many thanks! 

what confounds me, as early on in this set of posts, that the current behavior of stories with subtasks (i.e. subtask estimate times are NOT rolled up to the story) breaks the burndown chart, as the burndown chart target line displays the STORY orig estimate.  What are we doing wrong?

We are adding sub-tasks to a story to capture time estimates from the team, and had been capturing a time estimate at the story level for system testing time. I'm curious how others are capturing system test time needed and whether they are considering that part of the sprint effort or separate?

Is there any way to get story points (or whichever estimation used) total to appear in each column on the planning board (so we would see To Do x points, In Progress y points, Done z points etc?

I don't see the Estimation tab in my configure screen at all??

I don't see the Estimation tab in my configure screen at all??

Maybe someone can help me understand how this is supposed to work.

I have a project up and running, using Story Points as the estimation value and Time Tracking turned on.

Issues in the Backlog are all given Story Points and velocity is determined from there. All good. The question is about establishing remaining estimates at the beginning of a Sprint to let us do Tracking.

We drag our stories into the proposed Sprint. We create subtasks for each in order to break down the work and allow us to assign to multiple developers. The remaining estimates on the subtasks should roll up to the remaining estimates on the issue. Which they do, but only AFTER the Sprint starts. The problem I'm having is that BEFORE you start the sprint, you can only set Remaining Estimate on the issues and not the subtasks. And if we wait until after starting the Sprint to do our remaining estimation at the subtask level, any changes (from 0 to whatever) for Remaining Estimates counts as a scope change in the burndown chart.

What am I missing here? Do we have to set a Remaining Estimate at the issue level, THEN start the Sprint, THEN remove the issue level estimates while adding subtask estimates? That can't be right, can it?

Any advice would be appreciated.

Yes I have exactly the same problem, including the issue mentioned by others where a story runs across multiple releases and sprints, advice would be appreciated. 

I realize it's verboten in strict Kanban to use estimations but that's how we roll at my company. Could you please make the Kanban boards configurable for hourly/story point estimates. I'd owe you one.

Thx!

rb

Different question re tracking:

I'd like to try a burn down of story points pro-rata against the sub task completion. So say a story had 3 sub-tasks, and a story-point estimate of 9, each time a sub-task is resolved, the burn-down moves 3 points. We don't want to use time-tracking, and only estimate at the story level; but we think this might improve the ability to see if a sprint is on track.

To generalize, it sounds interesting to have some extension point for the value being graphed in burn-down charts. I.e. rather than burning down on a field, to be able to provide a plug-in to provide a value to burn-down on.

The documentation begins 

A common approach is to estimate tasks in Story Points, then track tasks using hours.

Prior to GH 6 one could have a burndown chart of the story points left and also the time left. Since one estimates in story points it is also common to see the story points burndown and also track the remaining time. To see both the story points burndown and also the remaining time one has to toggle the tracking statistic between none and Remaining Estimate and Time Spent. It should be possible to configure so both burndowns can be seen without having to toggle configuration.

I created a story for this, please vote:

GHS-9148 - Getting issue details... STATUS

If I add time to an issue via 'Log work' and chose a different date than the one given in 'Date Started' the time is not used in the Burndown Chart nor listed in the list below the chart.

Is this how it should be and in that case why? It messes things up if people forget to report time when they should.

If I add time to an issue via 'Log work' and chose a different date than the one given in 'Date Started' the time is not used in the Burndown Chart nor listed in the list below the chart.

Is this how it should be and in that case why? It messes things up if people forget to report time when they should.

Hi All

https://www.atlassian.com/software/greenhopper/overview mentions t-shirt estimation. How is it possible to configure such estimation with some statistics available?