Modify ↓

Opened 5 years ago

Closed 4 years ago

Last modified 4 years ago

#13643 closed defect (worksforme)

custom values not moved

Reported by: duytscal Owned by: Ryan J Ollos
Priority: normal Component: TicketMoverPlugin
Severity: normal Keywords:
Cc: Trac Release: 1.4

Description (last modified by duytscal)

The standard fields are copied/moved, but the custom fields do not reach the destination Trac.

Somewhere in the call new_ticket.insert() something goes wrong, because the custom fields are present in old_ticket.

What happens is that the Ticket.insert() method scans the list of fields known to the destination Trac in order to decide which values to copy.

this could also be a Trac issue: eg to allow unknown custom fields; but I'm not sure Trac is able to show those fields unless they have somehow been registered in the target Trac DB.

Attachments (0)

Change History (3)

comment:1 Changed 5 years ago by Ryan J Ollos

Owner: set to Ryan J Ollos
Status: new → accepted

comment:2 Changed 5 years ago by duytscal

Description: modified (diff)

comment:3 in reply to:  description Changed 4 years ago by Ryan J Ollos

Resolution: → worksforme
Status: accepted → closed

Replying to duytscal:

this could also be a Trac issue: eg to allow unknown custom fields; but I'm not sure Trac is able to show those fields unless they have somehow been registered in the target Trac DB.

That's right, the fields must be defined in the [ticket-custom] section of the target Trac. I believe that's proper behavior.

What is the use case for copying fields that aren't defined in the target Trac?

Last edited 4 years ago by Ryan J Ollos (previous) (diff)

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain Ryan J Ollos.
The resolution will be deleted. Next status will be 'reopened'.

Add Comment

E-mail address and name can be saved in the Preferences.

Attachments ↑ Description ↑
 
Note: See TracTickets for help on using tickets.