Modify

Opened 4 years ago

Last modified 4 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

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 tickettype == 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 (3)

comment:1 Changed 4 years ago by Chris Nelson

Interesting. Why/how would you use Trac without ticket types? I'm surprised that's possible!

comment:2 Changed 4 years ago by 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).

comment:3 in reply to:  2 Changed 4 years ago by Chris Nelson

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.

Modify Ticket

Change Properties
Set your email in Preferences
Action
as new The owner will remain Chris Nelson.

Add Comment


E-mail address and name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.