[JSWSERVER-8063] Board option for allowing sub issues to be treated as other issues

Type: Suggestion
Resolution: Answered
Fix Version/s: None
Component/s: AgileBoard
Labels:
None

Feedback Policy:

We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

NOTE: This suggestion is for JIRA Software Server. Using JIRA Software Cloud? See the corresponding suggestion.

The Atlassian way of handling sub issues is to only calculate their workload using time estimates. This is not how all teams work, and it would be nice to have an option on the board that lets you set if sub issues should be treated just like any other issue. This would broaden up the use of the rapid board for more of its users.

One problem with the current implementation is that story points on sub issues are not shown in the burndown chart. Any subissue is not shown in these charts at all. This makes statistics gathering somewhat hard to do if you treat issues in this way.

An added bonus would be if the combined value of the story points could be viewed on the parent issue as a calculated field. This calculated fields should not count towards the statistics of course.

is duplicated by

JSWSERVER-7992 Ability to see sub-tasks in the backlog

Gathering Interest

is related to

JSWSERVER-6868 Storypoints for sub tasks not showing in burndown

Closed

JSWSERVER-8152 Sub-tasks should not be included in Version Report

Closed

JSWSERVER-5212 As a Rapid Board User planning a project, I want the subtask estimates (both time and story points) to count towards my sprint marker estimates.

Gathering Interest

JSWSERVER-5614 Would like to see sub-tasks estimation in the main task on the Plan Mode of the Rapid Board

Gathering Interest

JSWSERVER-6007 Burndown chart doesn't take under consideration the sub-tasks estimation

Gathering Interest

relates to

JSWCLOUD-8063 Board option for allowing sub issues to be treated as other issues

Closed

(1 is related to, 1 relates to)

Leif Rask added a comment - 26/May/2021 6:46 AM

Not good. A valid use-case for sub-tasks is failed tests or related bugs arising while testing an issue. These should be child issues and also visible on the board for workflow resolution. Having them hidden inside the parent issue obscures the current state of developments underway.

At the moment, we have to create separate issues and "link" them back to the parent issue as a "relates to" or "blocks". In this manner, sub-tasks are a pointless feature.

Another valuable use-case for sub-tasks is tests to be conducted for an issue. It truly astounds me that Jira doesn't have any workflow for testing as part of issue tracking and resolution.

(I really wonder sometimes if Jira people actually use their own software)

Leif Rask added a comment - 26/May/2021 6:46 AM Not good. A valid use-case for sub-tasks is failed tests or related bugs arising while testing an issue. These should be child issues and also visible on the board for workflow resolution. Having them hidden inside the parent issue obscures the current state of developments underway. At the moment, we have to create separate issues and "link" them back to the parent issue as a "relates to" or "blocks". In this manner, sub-tasks are a pointless feature. Another valuable use-case for sub-tasks is tests to be conducted for an issue. It truly astounds me that Jira doesn't have any workflow for testing as part of issue tracking and resolution. (I really wonder sometimes if Jira people actually use their own software)

Martin (Inactive) added a comment - 01/May/2014 4:22 AM

Many thanks for reporting this issue, however allowing sub-tasks to be treated the same as standard issues is not something we plan to add to JIRA Agile at this time.
There are many aspects to sub-tasks which we will be looking to improve which are covered in other issues in the backlog including some linked to this story.

Regards,
JIRA Agile team

Martin (Inactive) added a comment - 01/May/2014 4:22 AM Many thanks for reporting this issue, however allowing sub-tasks to be treated the same as standard issues is not something we plan to add to JIRA Agile at this time. There are many aspects to sub-tasks which we will be looking to improve which are covered in other issues in the backlog including some linked to this story. Regards, JIRA Agile team

Jira Software Data Center

Details

Description

Attachments

Issue Links

Forms

Activity

Collapse comment: Leif Rask added a comment - 26/May/2021 6:46 AM

Expand comment: Leif Rask added a comment - 26/May/2021 6:46 AM

Collapse comment: Martin (Inactive) added a comment - 01/May/2014 4:22 AM

Expand comment: Martin (Inactive) added a comment - 01/May/2014 4:22 AM

People

Dates

Backbone Issue Sync