#9928 closed defect (cantfix)
BacklogTypeError: No backlog of type: Sprint Backlog
Reported by: | admin | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | general | Version: | 0.11.7 |
Severity: | normal | Keywords: | |
Cc: | support@… | Branch: | |
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
How to Reproduce
While doing a GET operation on /dashboard
, Trac issued an internal error.
(please provide additional details here)
User Agent was: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US) AppleWebKit/534.10 (KHTML, like Gecko) Chrome/8.0.552.215 Safari/534.10
System Information
Trac | 0.11.7
|
Python | 2.5.4 (r254:67916, Dec 23 2008, 15:10:54) [MSC v.1310 32 bit (Intel)]
|
setuptools | 0.6c9
|
SQLite | 3.3.4
|
pysqlite | 2.3.2
|
Genshi | 0.5.1
|
Agilo | 1.3.2-pro
|
Subversion | 1.5.6 (r36142)
|
jQuery: | 1.2.6
|
Python Traceback
Traceback (most recent call last): File "C:\Archivos de programa\Agilo\lib\site-packages\trac-0.11.7-py2.5-win32.egg\trac\web\main.py", line 450, in _dispatch_request dispatcher.dispatch(req) File "C:\Archivos de programa\Agilo\lib\site-packages\trac-0.11.7-py2.5-win32.egg\trac\web\main.py", line 206, in dispatch resp = chosen_handler.process_request(req) File "x:\agilo\lib\site-packages\binary_agilo-1.3.2_PRO-py2.5.egg\agilo\scrum\backlog\dashboard.py", line 109, in process_request File "x:\agilo\lib\site-packages\binary_agilo-1.3.2_PRO-py2.5.egg\agilo\scrum\backlog\dashboard.py", line 74, in _add_charts_to_template_data File "x:\agilo\lib\site-packages\binary_agilo-1.3.2_PRO-py2.5.egg\agilo\scrum\backlog\dashboard.py", line 55, in _get_sprint_backlog File "C:\Archivos de programa\Agilo\lib\site-packages\binary_agilo-1.3.2_pro-py2.5.egg\agilo\api\controller.py", line 361, in process_command return command.execute(self, date_converter, as_key) File "C:\Archivos de programa\Agilo\lib\site-packages\binary_agilo-1.3.2_pro-py2.5.egg\agilo\api\controller.py", line 315, in execute return self._execute(controller, date_converter, as_key) File "x:\agilo\lib\site-packages\binary_agilo-1.3.2_PRO-py2.5.egg\agilo\scrum\backlog\controller.py", line 51, in _execute File "C:\Archivos de programa\Agilo\lib\site-packages\binary_agilo-1.3.2_pro-py2.5.egg\agilo\scrum\backlog\model.py", line 574, in get return super(BacklogModelManager, self).get(**kwargs) File "C:\Archivos de programa\Agilo\lib\site-packages\binary_agilo-1.3.2_pro-py2.5.egg\agilo\core\model.py", line 1128, in get m = self.model(self.env, **kwargs) File "C:\Archivos de programa\Agilo\lib\site-packages\binary_agilo-1.3.2_pro-py2.5.egg\agilo\scrum\backlog\model.py", line 168, in __init__ raise BacklogTypeError("No backlog of type: %s" % name) BacklogTypeError: No backlog of type: Sprint Backlog
Attachments (0)
Change History (6)
comment:1 by , 14 years ago
Cc: | added |
---|---|
Resolution: | → cantfix |
Status: | new → closed |
follow-up: 3 comment:2 by , 14 years ago
@rblank: thanks for wrangling.
@reporter: please report to our google group (details on AgiloForScrum) - from a first look it seems that you may have removed the 'Sprint Backlog' type which would not be supported (though sadly possible through the configuration interface).
If thats indeed the case, try to restore it (look at defaults in a fresh agilo installation) and see if it helps.
comment:3 by , 14 years ago
Replying to Martin Häcker <martin.haecker@…>:
it seems that you may have removed the 'Sprint Backlog' type which would not be supported (though sadly possible through the configuration interface).
Check the required
flag on components (see r9458).
follow-up: 5 comment:4 by , 14 years ago
Great tip cboos!
Sadly 'Sprint Backlogs' are not components but just configured entities (more like ticket types in this regard) so we probably have to code this restriction ourselves. (Or I'm missing something. :)
comment:5 by , 14 years ago
Replying to Martin Häcker <martin.haecker@…>:
Or I'm missing something. :)
No, this required
flag indeed only applies to Component
s, I thought you were talking about the Plugins configuration interface in the WebAdmin. But for enforcing the preservation of a Ticket Type, well, feel free to propose a validation interface that we could add to the WebAdmin, so that plugins could veto some changes (a bit like the ITicketManipulator interface for individual ticket changes).
PluginIssue (AgiloForScrum).