Opened 11 years ago
Last modified 5 years ago
#11709 new defect
jsGantt needs priorities, ticket types and severities
Reported by: | Markus | Owned by: | Chris Nelson |
---|---|---|---|
Priority: | normal | Component: | TracJsGanttPlugin |
Severity: | normal | Keywords: | |
Cc: | Trac Release: | 1.0 |
Description (last modified by )
Removing all priorities, ticket types or severities from the ticket system makes the Trac jsGantt plugin unusable.
it fails with different error messages.
For example when all ticket types are removed I get this debugging error message:
File "build/bdist.linux-i686/egg/tracjsgantt/tracpm.py", line 473, in isMilestone return ticket['type'] == self.goalTicketType KeyError: 'type'
I would like to use Trac jsGantt plugin without priorities, ticket types or severities, but currently jsGantt can not handle these cases.
Trac_jsGantt-0.10_r13868 Trac 1.0.1
Attachments (0)
Change History (6)
comment:1 Changed 11 years ago by
comment:2 follow-up: 3 Changed 11 years ago by
Main reason is usability. Giving bugreporters less choices, they can concentrate on the important stuff: describing the bug or request and not focusing on questions like 'which priority should I give this report?'.
In Trac it is possible to delete the names of all priorities, ticket types or severities via the admin menu. For a smaller project I am currently working on, I don't need the added complexity of ticket types (they can be inferred from the ticket title easily).
comment:3 Changed 11 years ago by
Replying to Markus:
Main reason is usability. Giving bugreporters less choices, they can concentrate on the important stuff: describing the bug or request and not focusing on questions like 'which priority should I give this report?'.
In Trac it is possible to delete the names of all priorities, ticket types or severities via the admin menu. For a smaller project I am currently working on, I don't need the added complexity of ticket types (they can be inferred from the ticket title easily).
OK. I'll take a look at this when I have a chance.
comment:4 Changed 6 years ago by
I also encountered this issue today; removing all types causes the script to fail with:
File "/usr/local/lib/python2.7/dist-packages/Trac_jsGantt-1.2.0.0.dev0-py2.7.egg/tracjsgantt/tracpm.py", line 501, in isMilestone return ticket['type'] == self.goalTicketType KeyError: 'type'
Is there a way to resolve this, other than to add a ticket type?
comment:5 Changed 6 years ago by
Description: | modified (diff) |
---|
comment:6 Changed 5 years ago by
Here am I with 6 different ticket types, each with its only workflow...
Just add a ticket type!
Interesting. Why/how would you use Trac without ticket types? I'm surprised that's possible!