Opened 17 years ago
Closed 14 years ago
#4327 closed defect (wontfix)
csv2trac.2.py and priority values in comments.
| Reported by: | anonymous | Owned by: | Jonas Borgström |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | general | Version: | 0.10.2 |
| Severity: | normal | Keywords: | helpwanted |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
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 (0)
Change History (4)
comment:1 by , 17 years ago
| Summary: | csv2trac.2.py and severity → csv2trac.2.py and priority values in comments. |
|---|
comment:2 by , 17 years ago
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.
comment:3 by , 17 years ago
| Keywords: | helpwanted added |
|---|---|
| Milestone: | → 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)
comment:4 by , 14 years ago
| Milestone: | not applicable |
|---|---|
| Resolution: | → wontfix |
| Status: | new → closed |
If someone cares about the script, feel free to grab it and for example, create a NewHack.
Summary should talk about priority, not severity.