Ticket Merge

[tmote]

It appears that there may no longer be a method for merging duplicate tickets. It is not uncommon for one of our users to report an issue that has been reported by another user. In Cerb3.6, we merged the tickets and were able to keep both users up-to-date on the status with little work on our part.

Is there a new concept for this and I am just missing something? Or, is this a feature that may be coming?

[jstanden]

Hey Ty,

This is a bit hidden for simplicity, but it exists.

Click the 'More' link below your ticket list (to the right of the buttons).

[pk4]

I just tried out the ticket merging, and it's doing something i didn't expect.

I merged ticket A with ticket B
I tried searching on the ticket number from ticket A and it can't find it (search on ticket number from B works).

Is there any way that merged tickets can show up on both ticket numbers?

Also: is there some reason why the Content quick search is case sensitive?

Thanks!

[neenach2002]

Yea, I agree with pk4. There should be some sort of mask-reference to the new ticket.

Perhaps you could just change the ticket ID of the old ticket to the new one in the database, so they both call up the same ticket when searched.

[jstanden]

Hi pk4!

Is there any way that merged tickets can show up on both ticket numbers?

http://www.wgmdev.com/jira/browse/CHD-174

Also: is there some reason why the Content quick search is case sensitive?

What database (and DB version) are you using? e.g. MySQL 5, PostgreSQL 8

[pk4]

I'm using MySQL 5
Server version: 5.0.45-community-nt
MySQL client version: 5.0.45

Thanks!

[jstanden]

Also: is there some reason why the Content quick search is case sensitive?

Alright! I see the issue on a couple of those columns in the database. We still have a couple fields with the type BLOB (binary) that should be TEXT/CLOB (literal text). The BLOBs are being treated as case-sensitive.

Added a refactor task to the roadmap:
http://www.wgmdev.com/jira/browse/CHD-355