Merge bug?

Heya.

I’ve noticed a slight issues,
rt-2.0.11
If I merge two tickets together, then merge a third ticket into them, the
history shows all three tickets, but there is no transactions for the second
merge.

for this i,
merged 271419 into 271421
then resolved 271421
then merged 271420 into 271421

looking at the db it has…

mysql> select id,EffectiveId from Tickets where id in
(‘271419’,‘271420’,‘271421’);
| id | EffectiveId |
| 271419 | 271421 |
| 271420 | 271421 |
| 271421 | 271421 |
3 rows in set (0.00 sec)

which is correct, but…

mysql> select * from Transactions where Ticket in
(‘271419’,‘271420’,‘271421’) or EffectiveTicket in
(‘271419’,‘271420’,‘271421’);
| id | EffectiveTicket | Ticket | TimeTaken | Type | Field |
OldValue | NewValue | Data | Creator |
Created |
| 693415 | NULL | 271419 | 0 | Create | NULL |
NULL | NULL | NULL | 52 |
2002-01-17 12:24:09 |
| 693416 | NULL | 271420 | 0 | Create | NULL |
NULL | NULL | NULL | 52 |
2002-01-17 12:24:24 |
| 693418 | NULL | 271421 | 0 | Create | NULL |
NULL | NULL | NULL | 52 |
2002-01-17 12:24:43 |
| 693422 | NULL | 271419 | 0 | AddLink | MergedInto |
NULL | NULL | Ticket 271419 MergedInto ticket 271421. | 52 |
2002-01-17 12:25:35 |
| 693424 | NULL | 271421 | 0 | Status | Status | new
| resolved | NULL | 52 | 2002-01-17
12:25:58 |
5 rows in set (1.80 sec)

mysql>

so the second merge transaction is missing.

Anyone see this? is it a bug or just something I’m doing wrong.
So, it seems to work nicely, except, there is no transactions for subsequent
merges?

On a kind of related note, I noticed with 2.0.9 when doing a search it must
not look at the effectiveids correctly, as a search would pull out tickets
that are merges together… but that seems to be fixed in 2.0.11

Matthew Watson
Development, Netspace Online Systems
mwatson@netspace.net.au

As an afterthought, i turned on debug and merged another ticket into my 3
merged tickets.

had a looky in the debug logs…

checking if the new ticket has the same id and effective id…adding a
merged into linkRT::Ticket=HASH(0x9019790) Somebody tried to duplicate a
link

The merge actually succeeded, but the AddLink failed.

Hello,
I’ve taken a look at the mailing list archives and this issue seems to
be unresolved.
Does someone have more infos?
I have exactly the same problem… the ticket is merged but no
transaction is generated.
Regards
Rafael

Thu, 17 Jan 2002 13:03:27 +1100

As an afterthought, i turned on debug and merged another ticket into my
3
merged tickets.

had a looky in the debug logs…

checking if the new ticket has the same id and effective id…adding a
merged into linkRT::Ticket=HASH(0x9019790) Somebody tried to duplicate a
link

The merge actually succeeded, but the AddLink failed.

-----Original Message-----
From: rt-users-admin@lists.fsck.com
[mailto:rt-users-admin@lists.fsck.com]On Behalf Of Matthew Watson
Sent: Thursday, 17 January 2002 12:36 PM
To: rt-users@lists.fsck.com
Subject: [rt-users] merge bug?

Heya.

I’ve noticed a slight issues,
rt-2.0.11
If I merge two tickets together, then merge a third ticket into them,
the
history shows all three tickets, but there is no transactions for
the second
merge.

for this i,
merged 271419 into 271421
then resolved 271421
then merged 271420 into 271421

looking at the db it has…

mysql> select id,EffectiveId from Tickets where id in
(‘271419’,‘271420’,‘271421’);
±-------±------------+
| id | EffectiveId |
±-------±------------+
| 271419 | 271421 |
| 271420 | 271421 |
| 271421 | 271421 |
±-------±------------+
3 rows in set (0.00 sec)

which is correct, but…

mysql> select * from Transactions where Ticket in
(‘271419’,‘271420’,‘271421’) or EffectiveTicket in
(‘271419’,‘271420’,‘271421’);
±-------±----------------±-------±----------±--------±------
-----±—
------±---------±----------------------------------------±-----
—±-----
---------------+
| id | EffectiveTicket | Ticket | TimeTaken | Type | Field
|
OldValue | NewValue | Data |
Creator |
Created |
±-------±----------------±-------±----------±--------±------
-----±—
------±---------±----------------------------------------±-----
—±-----
---------------+
| 693415 | NULL | 271419 | 0 | Create | NULL
|
NULL | NULL | NULL |
52 |
2002-01-17 12:24:09 |
| 693416 | NULL | 271420 | 0 | Create | NULL
|
NULL | NULL | NULL |
52 |
2002-01-17 12:24:24 |
| 693418 | NULL | 271421 | 0 | Create | NULL
|
NULL | NULL | NULL |
52 |
2002-01-17 12:24:43 |
| 693422 | NULL | 271419 | 0 | AddLink | MergedInto
|
NULL | NULL | Ticket 271419 MergedInto ticket 271421. |
52 |
2002-01-17 12:25:35 |
| 693424 | NULL | 271421 | 0 | Status |
Status | new
| resolved | NULL | 52 |
2002-01-17
12:25:58 |
±-------±----------------±-------±----------±--------±------
-----±—
------±---------±----------------------------------------±-----
—±-----
---------------+
5 rows in set (1.80 sec)

mysql>

so the second merge transaction is missing.

Anyone see this? is it a bug or just something I’m doing wrong.
So, it seems to work nicely, except, there is no transactions for
subsequent
merges?

On a kind of related note, I noticed with 2.0.9 when doing a
search it must
not look at the effectiveids correctly, as a search would pull out
tickets