This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 68588 - User Tasks lose Summary and Details
Summary: User Tasks lose Summary and Details
Status: VERIFIED FIXED
Alias: None
Product: contrib
Classification: Unclassified
Component: Tasklist (show other bugs)
Version: 5.x
Hardware: PC Windows XP
: P1 blocker (vote)
Assignee: Tim Lebedkov
URL:
Keywords:
: 68282 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-11-12 14:52 UTC by jimkatz
Modified: 2008-03-12 11:11 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Document to store user tasks (1.18 KB, text/plain)
2005-11-12 14:54 UTC, jimkatz
Details

Note You need to log in before you can comment on or make changes to this bug.
Description jimkatz 2005-11-12 14:52:18 UTC
I downloaded the latest Task List module from the download center. It appeared
to install and be working normally. I entered several known issues for my
project. This morning after opening Netbeans I find that the User Tasks are
still there but the critical data in the Summary and Details fields are missing.
Is there something I'm missing here? Like another step to save the data? 
Further testing revealed that closing the User Tasks window would cause the same
behavior, i.e. the tasks lose the summary and detail field data previously entered.

Q Build 200510311820
Comment 1 jimkatz 2005-11-12 14:54:50 UTC
Created attachment 26888 [details]
Document to store user tasks
Comment 2 Tim Lebedkov 2005-11-14 18:41:13 UTC
cannot reproduce with the current dev build
Comment 3 Torbjorn Norbye 2005-11-14 18:45:52 UTC
This just happened for me last week too. And I use a dev build of NetBeans 5.0.  (I pull and rebuild 
every day or two).

So unless this has been fixed in the tasklist module in the last week it's still there, although perhaps not 
100% reproducible.

I have a tasklist with a bunch of tasks in it, and out of 35 tasks, 4 have no Summary any more. I know I 
didn't enter them that way (although it's very easy to do so in the New Task dialog; I should file a 
usability bug on that), and a couple of days later I spotted a new blank task.   

I'm a bit worried since I don't know -which- tasks were dropped. Hopefully nothing important. We've 
gotta track this down.
Comment 4 Torbjorn Norbye 2005-11-14 19:05:50 UTC
By the way, note that all my "blank" tasks are at the END of the tasklist (and I don't have Summary sorting 
enabled, it's in natural (reverse entered) order).  Don't know if that clue helps.   The way I know these are 
real tasks as opposed to accidentally entered blank tasks is that the Category fields still contain their 
contents.
Comment 5 Tim Lebedkov 2005-11-14 20:51:07 UTC
Glad to hear you again Tor.

There was indeed a commit for ICalExportFormat.java on 10 Nov (1.15)

here is the old code:
            if (prop == null)
                prop = new Summary();


            prop.setValue(desc);
        } else {
            if (prop != null)
                pl.remove(prop);
        }

        // description (details)
        String details = task.getDetails();
        prop = pl.getProperty(Property.DESCRIPTION);
        if (details != null && details.length() > 0) {
            if (prop == null)
                prop = new Description();


            prop.setValue(details);

and here the new (the new CVS support seems to lack the ability to produce
text diffs and I already deinstalled WinCVS):
            if (prop == null) {
                prop = new Summary();
                pl.add(prop); <<<<<<<<<<<<<<<<<<<<<<<<<
            }
            prop.setValue(desc);
        } else {
            if (prop != null)
                pl.remove(prop);
        }

        // description (details)
        String details = task.getDetails();
        prop = pl.getProperty(Property.DESCRIPTION);
        if (details != null && details.length() > 0) {
            if (prop == null) {
                prop = new Description();
                pl.add(prop);<<<<<<<<<<<<<<<<<<<<<<<<<
            }

closing the issue as "fixed".

Comment 6 Tim Lebedkov 2005-11-14 20:53:12 UTC
*** Issue 68282 has been marked as a duplicate of this issue. ***
Comment 7 Tim Lebedkov 2008-03-12 11:11:05 UTC
6.0 is out