Bug 229554 - general bugginess distinguishing subtasks and deleting events
Summary: general bugginess distinguishing subtasks and deleting events
Status: RESOLVED WORKSFORME
Alias: None
Product: ktimetracker
Classification: Applications
Component: general (show other bugs)
Version: 4.5.x
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: Thorsten Staerk
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-05 15:34 UTC by nick
Modified: 2011-02-26 22:00 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description nick 2010-03-05 15:34:01 UTC
Version:           4.4.1 (using KDE 4.4.1)
OS:                Linux
Installed from:    Gentoo Packages

If multiple subtasks of *different* parent tasks have the same name, their elapsed times are accumulated together for all parents involved.

eg:
Task 1
- subtask 1
Task 2
- subtask 1

It doesn't seem to distinguish between who owns which of the two "subtask 1" entries, and events from either get summed for each of Task 1 and Task 2.

Deleting individual events from either of the "subtask 1" entries will affect the totals of both Task 1 and Task 2.

However, there's a _huge_ usability issue with the edit times--there is no way of knowing which "subtask 1" an event belongs to--it's not displayed.
It seems that the event code assumes that all tasks and subtasks combined in the ktt will have unique names, which isn't true.

I'd suggest doing something like:
Task 1:subtask 1
Task 2:subtask 1
at the very least to distinguish.
Comment 1 nick 2010-03-05 15:48:24 UTC
This bug may explain some of the behavior that I observed and reported in bug 169660.

When several subtasks were started up (from different tasks), it's likely that they had the same name in common, which might explain their connection.

Also, for this bug, when I opened up the times editor, there were dozens of events from subtasks that I had already deleted still in the list--and stranger still, their times were being counted with in the task totals...
As I deleted these events, the task totals were adjusted accordingly, so that's good at least.
Comment 2 Thorsten Staerk 2010-03-07 10:12:49 UTC
Please give steps how to reproduce. I understand your report like this:

0. start with an empty ktimetracker
1. create a task a
2. create a task b
3. create a task sub1, subtask to a
4. create a task sub1, subtask to b
5. start timing for a/sub1
6. wait 3 minutes

expected result:
a/sub1 shows 3 minutes
b/sub1 shows 0 minutes

what you see:
a/sub1 shows 3 minutes
b/sub1 shows 3 minutes
Comment 3 nick 2010-03-07 10:43:29 UTC
I had already quit and restarted ktt several times since creating the tasks and subtasks.
I opened it once, and all-of-a-sudden they were wrong.
I went to edit the event times, and discovered there were a bunch of event times for subtasks that I had already deleted (and they no longer showed in the gui as subtasks). Also, I deleted the ones with duplicate names, since I was done with them anyways. As I did so, the times on the tasks corrected themselves.

I don't know the exact steps to reproduce it. That's why I described it as "general bugginess". It was definitely somehow in an invalid state.