Opened 11 years ago
Last modified 11 years ago
#11595 new defect
KeyError: 'peer review'
Reported by: | Owned by: | Andrea Tomasini | |
---|---|---|---|
Priority: | normal | Component: | AgiloForTracPlugin |
Severity: | normal | Keywords: | |
Cc: | Trac Release: | 1.0 |
Description
How to Reproduce
While doing a GET operation on /backlog/Release Backlog
, Trac issued an internal error.
We have a rather 'vanilla' install of Agilo for Trac and I came in this morning and assigned a user story to a milestone (called "Release 1.0.0"). Then I went to look at the backlog for that milestone, and got the error. I do not know if the error already existed before I added the story, or if my change was the cause of the problem. Now, regardless if I remove or add that story to the backlog it is still showing the error. I am not sure how to proceed.
Request parameters:
{'bscope': u'Release 1.0.0', 'name': u'Release Backlog', 'scope': None, 'view': u'View'}
User agent: #USER_AGENT#
System Information
Trac | 1.0.1
|
Agilo | 0.9.12
|
Genshi | 0.6 (with speedups)
|
mod_python | 3.3.1
|
pysqlite | 2.6.0
|
Python | 2.7.3 (default, Sep 26 2013, 20:13:52) [GCC 4.6.3]
|
setuptools | 0.6
|
SQLite | 3.7.9
|
jQuery | #JQUERY#
|
Enabled Plugins
agilo | 0.9.12
|
binary-agilo | 1.3.12-PRO
|
TracAccountManager | 0.5dev-r13381
|
Python Traceback
Traceback (most recent call last): File "/usr/local/lib/python2.7/dist-packages/Trac-1.0.1-py2.7.egg/trac/web/main.py", line 497, in _dispatch_request dispatcher.dispatch(req) File "/usr/local/lib/python2.7/dist-packages/Trac-1.0.1-py2.7.egg/trac/web/main.py", line 214, in dispatch resp = chosen_handler.process_request(req) File "/usr/local/lib/python2.7/dist-packages/agilo-0.9.12-py2.7.egg/agilo/api/view.py", line 155, in process_request return self._call_filters_and_handler(req, handler) File "/usr/local/lib/python2.7/dist-packages/agilo-0.9.12-py2.7.egg/agilo/api/view.py", line 143, in _call_filters_and_handler data = handler(req) or {} File "/usr/local/lib/python2.7/dist-packages/agilo-0.9.12-py2.7.egg/agilo/scrum/backlog/web_ui.py", line 326, in do_get backlog_table = renderer.get_backlog_table_html(req.href()) File "/usr/local/lib/python2.7/dist-packages/agilo-0.9.12-py2.7.egg/agilo/scrum/backlog/backlog_renderer.py", line 230, in get_backlog_table_html for item in self.get_top_level_containers(): File "/usr/local/lib/python2.7/dist-packages/agilo-0.9.12-py2.7.egg/agilo/scrum/backlog/backlog_renderer.py", line 73, in get_top_level_containers if self.ticket_is_container(item.ticket) and not self.ticket_has_parents(item.ticket): File "/usr/local/lib/python2.7/dist-packages/agilo-0.9.12-py2.7.egg/agilo/scrum/backlog/backlog_renderer.py", line 62, in ticket_is_container if len(self.configured_child_types_for_type(ticket_type)) != 0: File "/usr/local/lib/python2.7/dist-packages/agilo-0.9.12-py2.7.egg/agilo/scrum/backlog/backlog_renderer.py", line 53, in configured_child_types_for_type for possible_child in self.link_tree[ticket_type]: KeyError: 'peer review'
Attachments (1)
Change History (5)
comment:1 Changed 11 years ago by
Changed 11 years ago by
comment:2 Changed 11 years ago by
I uploaded our trac.ini (unmodified). I notice in that file in the [agilo-types] section the items for "peer_review" and "peer_review.alias", however I do not see those in my Agilo/Trac Administration page under "Types". I do see all the other ones listed (Big Story, Bug, Requirement, User Story, Task).
comment:3 Changed 11 years ago by
We "fixed" this problem. The Ticket Type "peer review" was removed because we do not use it. But this caused an exception somewhere when looking at our Release Backlog. By re-adding the 'peer review' Ticket Type, the system works correctly again.
comment:4 Changed 11 years ago by
Hi there. It's possible that the space in the alias of the ticket type was causing it not to show up properly. Can you confirm this is happening also for the "Big story" ticket type? Do you see any error/warning about these types in the trac log file?
Hi Benjamin, can you please attach the trac.ini file for your installation? Make sure you remove any sensitive information first.