Opened 8 years ago

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

Reported by: Owned by: trac@… François Granade low TicketImportPlugin minor 1.0

### 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?

### comment:1 Changed 8 years ago by Willy

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.

### comment:2 Changed 8 years ago by Steffen Hoffmann

Priority: highest → low blocker → normal Import fail with: Ticket 1540 found in file, but not present in Trac: cannot import. → 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

### comment:3 Changed 8 years ago 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.

### comment:4 Changed 7 years ago by François Granade

Resolution: → wontfix new → closed

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.

### comment:5 Changed 5 years ago by rendus@…

Resolution: wontfix normal → minor closed → reopened 0.11 → 1.0 defect → enhancement

This is really awful to find, searching Google, when I follow the documentation that states the following:

The only required fields are either:

summary. If tickets are found in Trac with the same 'summary', they will be reconciliated: no ticket will be added, but modified or added values for other fields, will be imported (of course, any replaced value is always kept in the Change History for the ticket). As a consequence, you cannot have two tickets (or two rows in your spreadsheet) with the same summary . If the summary doesn't match any existing ticket, a new ticket will be created.
or:
ticket. This field should contain ticket numbers: if tickets are found with the same number, they will be reconciliated. If it is empty for some rows, they will be imported as new tickets. This can be used to export (using a report and save as CSV), modify in Excel, and re-import tickets.


Fix the plugin to not give false information, please.

### comment:6 Changed 5 years ago by anonymous

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?

### Modify Ticket

Change Properties