typing cluelessly at the demo, trying to enter a new issue... 
 
How to repeat: 
 
Issues: Create New 
Enter title: test1 
Select Priority: bug 
Enter Superseder: super 
 
Hit "Submit New Entry" button 
 
The following traceback occurs: 
 
Templating Error 
 
 
exceptions.TypeError: No key property set for class issue 
 
 
Debugging information follows 
 
In python expression "context.superseder.field(showid=1, 
size=20)" 
While evaluating the expression on line 45  
 
Current variables: 
 
 
templates 
<roundup.cgi.templating.Templates instance at 0x832f5c4> 
 
 
repeat 
<roundup.cgi.PageTemplates.TALES.SafeMapping instance at 
0x83ebf3c> 
 
 
default 
<roundup.cgi.PageTemplates.TALES.Default instance at 
0x815015c> 
 
 
db 
<roundup.cgi.templating.HTMLDatabase instance at 0x846e1e4> 
 
 
utils 
<roundup.cgi.templating.utils instance at 0x82ffc44> 
 
 
request 
<roundup.cgi.templating.HTMLRequest instance at 0x82f564c> 
 
 
tracker 
<module '_roundup_tracker_1' from 
'/home/harri/downloads/roundup-0.6.6/demo/__init__.pyc'> 
 
 
context 
<HTMLClass(0x8415e24) issue> 
 
 
nothing 
None 
 
 
config 
<module '_roundup_tracker_1.config' from 
'/home/harri/downloads/roundup-0.6.6/demo/config.pyc'> 
 
 
options 
{'ok_message': [], 'error_message': ['Error: you may only enter 
ID values for property "superseder": No key property set for 
class issue']} 
 
 
loop 
<roundup.cgi.PageTemplates.TALES.SafeMapping instance at 
0x83ebf3c> 
 
 
attrs 
{'tal:replace': 'structure 
python:context.superseder.field(showid=1, size=20)'} 
 
A problem occurred in your template "issue.item.html". 
 
Full traceback: 
 
 
Traceback (most recent call last): 
  File "roundup/cgi/client.py", line 526, in renderContext 
    result = pt.render(self, None, None, **args) 
  File "roundup/cgi/templating.py", line 216, in render 
    getEngine().getContext(c), output, tal=1, strictinsert=0)() 
  File "roundup/cgi/TAL/TALInterpreter.py", line 154, in __call__ 
    self.interpret(self.program) 
  File "roundup/cgi/TAL/TALInterpreter.py", line 186, in interpret 
    handlers[opcode](self, args) 
  File "roundup/cgi/TAL/TALInterpreter.py", line 525, in 
do_useMacro 
    self.interpret(macro) 
  File "roundup/cgi/TAL/TALInterpreter.py", line 186, in interpret 
    handlers[opcode](self, args) 
  File "roundup/cgi/TAL/TALInterpreter.py", line 549, in 
do_defineSlot 
    self.interpret(slot) 
  File "roundup/cgi/TAL/TALInterpreter.py", line 186, in interpret 
    handlers[opcode](self, args) 
  File "roundup/cgi/TAL/TALInterpreter.py", line 491, in 
do_condition 
    self.interpret(block) 
  File "roundup/cgi/TAL/TALInterpreter.py", line 186, in interpret 
    handlers[opcode](self, args) 
  File "roundup/cgi/TAL/TALInterpreter.py", line 432, in 
do_insertStructure_tal 
    structure = self.engine.evaluateStructure(expr) 
  File "roundup/cgi/PageTemplates/TALES.py", line 225, in 
evaluate 
    v = expression(self) 
  File "roundup/cgi/PageTemplates/PythonExpr.py", line 71, in 
__call__ 
    return f() 
  File "<string>", line 2, in f 
  File "roundup/cgi/templating.py", line 342, in __getattr__ 
    return self[attr] 
  File "roundup/cgi/templating.py", line 319, in __getitem__ 
    handleListCGIValue(form[item])) 
  File "roundup/cgi/templating.py", line 258, in lookupIds 
    l.append(cl.lookup(entry)) 
  File "roundup/backends/back_anydbm.py", line 1476, in lookup 
    raise TypeError, 'No key property set for class 
%s'%self.classname 
TypeError: No key property set for class issue 
 

Logged In: YES 
user_id=6405

The superseder field only accepts issue ids. Try using the 
(list) popup. 
 
Unfortunately, the error is not handled well during issue 
creation (it is handled sanely during issue editing). I'll look 
into fixing the handling for the next bugfix release. 
 

Logged In: YES 
user_id=6405

I've checked a fix into CVS that makes the behaviour of 
failure under creation much nicer.