Modify

Opened 10 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 (last modified by Ryan J Ollos)

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 10 years ago by Chris Nelson

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

comment:2 Changed 10 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 10 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.

comment:4 Changed 5 years ago by Marco

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 5 years ago by Ryan J Ollos

Description: modified (diff)

comment:6 Changed 4 years ago by anonymous

Here am I with 6 different ticket types, each with its only workflow...

Just add a ticket type!

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.