Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

where is "Other"

yoshi0214 September 5, 2020

I want to add a subtask as burndown. "Other" is nothing

the following help is old??

<https://ja.confluence.atlassian.com/jirasoftwarecloud/configuring-estimation-and-tracking-764478030.html>

 

VET ボード - アジャイル ボード - Jira - Google Chrome 2020-09.png

 

4 required for burndown

VET ボード - アジャイル ボード - Jira - Google Chrome 2020-09.png

Go only one

VET ボード - アジャイル ボード - Jira - Google Chrome 2020-09.png

1 answer

1 accepted

1 vote
Answer accepted
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 5, 2020

Could you explain what you are talking about when you say "where is other" and "other is nothing"?

As for "I want to add subtask as burndown", I think you're misunderstanding what scrum and burndown are for.  You do not burn down on sub-tasks.

yoshi0214 September 5, 2020

Thanks :)

I may not be understanding of 'Jira' project management.

 

1: I created a task, and then three subtasks for each person. OK, sum is 80.

1.png

 

2: Yes, 'Epic' it easy to see as 5 people are stored in one task.2.png

 

 

3: I looked at the burndown chart. Ooops!! All or nothing!!

3.png

 

Was my usage wrong?

I wanted to make it smart with Epic and display it in detail on the burndown chart.

Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 5, 2020

Ok, the simple thing here is that you do not put Scrum estimates on sub-tasks.  Burn-down is exactly what you see here - all or nothing on each item you committed to doing in the sprint (not the subtasks)

Like yoshi0214 likes this
yoshi0214 September 5, 2020

understood.
I think the estimation of subtasks should be think as breakdown (i.g. the Numbers do not affect the burndown chart) for the tasks displayed in the burndown chart.

If I want to see an estimate of the breakdown, displayed in the burndown chart, define everything as a task(not subtasks), and if the task has growing, define it as a new task.

I have a friend who manages numerical values ​​when there are more jira tasks in the `spreadsheet`, so I tell friend about it.

Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 6, 2020

The breakdown chart you describe is nothing to do with burndown, so I'd expect to see them separately.

yoshi0214 September 6, 2020

OK, this is finished. :)

thanks a lot.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
TAGS
AUG Leaders

Atlassian Community Events