[#JRA-14673] Issue "Remaining Estimate" does not deduct "Sub-Task" original estimate for Sub-Tasks which are resolved.

JIRA

Issue "Remaining Estimate" does not deduct "Sub-Task" original estimate for Sub-Tasks which are resolved.

Created: 19/Mar/08 07:37 AM Updated: 24/Mar/08 08:10 PM

Component/s:

Time Tracking

Affects Version/s:

3.11

Fix Version/s:

None

Time Tracking:

Not Specified

Issue Links:

Duplicate

This issue duplicates:

JRA-1993 Resolving an issue should automatically put the estimated time remaining to 0

Participants:	Anton Mazkovoi [Atlassian] and Dominick More
Since last comment:	23 weeks, 6 days ago
Resolution Date:	24/Mar/08 08:10 PM
Labels:	audatex

Description

« Hide

When a "Sub-Task" is resolved the full "original estimate" should be deducted from the parent issue "Remaining Estimate" regardless of the "Work log" entries of the "Sub-Task". We don't force our users to enter work logs but we do force them to enter the "original estimate" so we can leverage the timetracking functionality to schedule releases.

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Anton Mazkovoi [Atlassian] added a comment - 19/Mar/08 10:32 PM

Hi Dominick,

I see what you mean.

One of JIRA's major strengths is that the workflows can be customised. Therefore it is difficult for us to enforce when the estimates should be deducted.

I believe a good solution to this problem is implementing JRA-1993. Therefore, when a sub-task is resolved, its remaining estimate will drop to 0 and the parent's totals will also be adjusted.

On more technical level, the parent issue does not actually store the totals. They are calculated on the fly each time, based on the sub-tasks. This is needed, as a user might not be able to see all sub-tasks.

Therefore, I would like to resolve this issue as a duplicate of JRA-1993.

Cheers,
Anton

[ Permlink | « Hide ]

Dominick More added a comment - 20/Mar/08 09:48 AM

Really this shouldn't be such a complicated task. Just have to omit all subtasks where resolution is not empty. Just as well I think I will change the source myself as the duplicate issue is almost 5 years old!!!

[ Permlink | « Hide ]

Anton Mazkovoi [Atlassian] added a comment - 24/Mar/08 08:09 PM

Hi Dominick,

Really this shouldn't be such a complicated task.

Esentially you are right. However, I believe this is the wrong place for fixing this problem.

I do believe fixing JRA-1993 is the right way to approach it. The main issue we have with fixing JRA-1993 is that it breaks old behaviour and may cause some users problems when they upgrade, especially when custom workflows are in use (which is very often). However, it looks like the benefits will outweigh the costs, so I am hoping to resolve JRA-1993 in one of the next releases.

I will resolve this issue as a duplicate.

Cheers,
Anton