When using the "make a copy" link on a customized tracker (release 1.3.2) where two custom data have been added according to the customize docs, Roundup throws a template exception.

The two added data are a due_date and a timelog done according to the docs.

The error is:
exceptions.IndexError: no such timelog node 2

The exception traceback final lines are:
  File "C:\Programs\Python\lib\site-packages\roundup\cgi\templating.py", line 809, in __getitem__
    value = self._klass.get(self._nodeid, items[0], None)
  File "C:\Programs\Python\lib\site-packages\roundup\backends\rdbms_common.py", line 1460, in get
    d = self.db.getnode(self.classname, nodeid)
  File "C:\Programs\Python\lib\site-packages\roundup\backends\rdbms_common.py", line 950, in getnode
    raise IndexError, 'no such %s node %s'%(classname, nodeid)
IndexError: no such timelog node  2

Apparently something happens behind the link that is not handled by the customization, and it has to do with the timelog data.

I tried to reproduce this with the current CVS and "it worked for me".

I added a due_date and timelog per customizing.txt, created an issue with a timelog and due_date and then clicked "Make a copy".

The copied issued didn't copy the timelog -- just the due_date.

If you could post step-by-step instructions of how to reproduce this, that would be great. If you could do it on roundup 1.3.3 or CVS it would be even greater :)