New and Improved 3.13 Beta. Highlights: Shareable filters and dashboards and lots of other goodies. Any feedback can be raised as JIRA issues in the JIRA project.
Issue Details (XML | Word | Printable)

Key: JRA-14685
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Dushan Hanuska [Atlassian]
Reporter: Danita Day
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
JIRA

version workload report shows a subtask that is resolved

Created: 20/Mar/08 03:20 PM   Updated: 25/Mar/08 03:04 AM
Component/s: Reports, Sub-tasks
Affects Version/s: 3.12.1
Fix Version/s: 3.12.3

Time Tracking:
Original Estimate: 2 hours
Original Estimate - 2 hours
Remaining Estimate: 0 minutes
Time Spent - 2 hours
Time Spent: 2 hours
Time Spent - 2 hours

Environment:
Application Server: Apache Tomcat/5.5.20
Servlet Version: 2.4
Edition: Enterprise
Version: 3.12.1
Build Number: 299
Installation Type: Standalone

Participants: Danita Day and Dushan Hanuska [Atlassian]
Since last comment: 22 weeks, 6 days ago
Resolution Date: 25/Mar/08 03:04 AM
Labels:


 Description  « Hide
Version Workload Report Selections
Display unestimated issues - yes
Sub-task inclusion: Including all subtasks

Report shows a subtask that is resolved. I noticed the parent task (which is also part of this version) is not resolved.
This is because other outstanding subtasks of this parent are still in progress.

All subtasks have estimates and have the fix version set properly.

IF I change
Sub-task inclusion : Only including sub-task with the selected version

The resolved subtask does NOT show up.

This doesn't make any sense. Somehow I think this bug is related to the parent not being resolved because all of the other subtask I have as resolved AND the parent is resolved do not show up in the report no matter what the Sub-task Inclusion field is set to.



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
There are no comments yet on this issue.