Ticket #5504 (closed defect: wontfix)

Opened 3 years ago

Last modified 2 years ago

importing new tickets with arbitrary pre-defined number rejected by trac

Reported by: trac@scottpthompson.com Assigned to: farialima
Priority: low Component: TicketImportPlugin
Severity: normal Keywords:
Cc: Trac Release: 0.11

Description

Error: Ticket 1540 found in file, but not present in Trac: cannot import.

Trying a simple one ticket import file. It seems to be trying to work but instead of adding it is failing out because it can not find the ticket.

perhaps there is a setting somewhere I am missing?

Attachments

Change History

08/14/09 19:37:41 changed by advicepig

I had the same error when importing tickets from another system. It appears that the plugin will only create new tickets with new numbers or update old tickets.

So I created a csv that had just one column, summary. I filled that column with sequential numbers so there were as many rows as I needed to create tickets up to the right number of rows. I imported this to create a ton of tickets.

After that worked, I imported the csv with my real tickets and it updated each of the fake tickets to be what I expected in the first place.

A little cleanup on the empty tickets followed, but it was faster than anything else I came up with.

02/26/10 21:56:01 changed by hoff.st@web.de

  • priority changed from highest to low.
  • severity changed from blocker to normal.
  • summary changed from Import fail with: Ticket 1540 found in file, but not present in Trac: cannot import. to importing new tickets with arbitrary pre-defined number rejected by trac.

well, certainly Trac insists on giving ticket ids on it's own, what makes perfectly sense to avoid (even the need to deal with) duplicates in it's ticket database, bug is more on users side, requesting something Trac itself (the real source of the error message) can't (shouldn't?) allow - simply don't try to predefine new ticket numbers, so IMHO neither plugin nor it's author are to be blamed for the situation

lowering priority, developer(s) or maintainer may even decide to set this to fix:invalid or fixed:wontfix

02/27/10 02:27:32 changed by anonymous

Have to say definitely disagree especially since there is an option for existing numbers in the module. However since it has been 8 months really not much relevance anymore.

04/23/10 20:24:07 changed by farialima

  • status changed from new to closed.
  • resolution set to wontfix.

I'm afraid that this is not possible to implement. I understand what you want to do, but the main goal of this plugin is letting you edit your tickets in Excel, and re-import them: not migrate from one system to another. Closing as wontfix, but documenting on the home page.

Add/Change #5504 (importing new tickets with arbitrary pre-defined number rejected by trac)




Change Properties
Action