Modify ↓
Opened 15 years ago
Last modified 15 years ago
#6034 new defect
imported milestone column not handled, if no milestone present
Reported by: | terje | Owned by: | François Granade |
---|---|---|---|
Priority: | low | Component: | TicketImportPlugin |
Severity: | minor | Keywords: | |
Cc: | Trac Release: | 0.11 |
Description
Summary pretty much says it all - if there are no components, the milestone column will not be handled. (As if it was not present in file).
Trac 0.11.5stable-r8357
Attachments (0)
Change History (4)
comment:1 Changed 15 years ago by
comment:2 Changed 15 years ago by
Summary: | Milestone column not detected if no components present → Milestone column not detected if no milestones present |
---|
comment:3 Changed 15 years ago by
Summary: | Milestone column not detected if no milestones present → imported milestone column not handled, if no milestone present |
---|
comment:4 Changed 15 years ago by
Priority: | normal → low |
---|
This is kind of as-designed: you may have noted that if no milestone is present in Trac, then the milestone column does not appear *at all* anywhere in the UI. The help tells you that in the admin, in fact.
So the workaround is to create one milestone (any milestone) and then do the import.
Lowering the priority, but keeping open - ideally it should propose you to import.
Note: See
TracTickets for help on using
tickets.
Sorry, incorrect conclusion while in a rush ;-( In fact, milestone column is not detected if no milestones are present in trac. Makes more sense ;-)