Edgewall Software

Ticket #4327 (new defect)

Opened 2 years ago

Last modified 20 months ago

csv2trac.2.py and priority values in comments.

Reported by: anonymous Owned by: jonas
Priority: normal Milestone: not applicable
Component: general Version: 0.10.2
Severity: normal Keywords: helpwanted
Cc:

Description

http://trac.edgewall.org/attachment/wiki/TracSynchronize/csv2trac.2.py#L42 lists that following values that are allowed for priority

priority must be one of: highest, high, normal, low, lowest

However these values are correct:

blocker, critical,major, minor,trivial 

Also csv2trac2.py seems to be 7 months old, is it still up to date?

And yet another question: is there an API for this kind of importers?

Attachments

Change History

Changed 2 years ago by anonymous

  • summary changed from csv2trac.2.py and severity to csv2trac.2.py and priority values in comments.

Summary should talk about priority, not severity.

Changed 2 years ago by anonymous

This is a problem when using SQLLite database. If I put value normal to ticket.priority, import script will not give any errors. The result is that some reports will not show imported tickets, because they make a JOIN to enum table.

Changed 20 months ago by cboos

  • keywords helpwanted added
  • milestone set to none

This is a contributed script which is not maintained by us.

(if other devs prefer to close this as wontfix, I won't mind)

Add/Change #4327 (csv2trac.2.py and priority values in comments.)

Author



Change Properties
<Author field>
Action
as new
as The resolution will be set. Next status will be 'closed'
to The owner will change from jonas. Next status will be 'new'
The owner will change from jonas to anonymous. Next status will be 'assigned'
 
Note: See TracTickets for help on using tickets.