I have tried in the past, to add this functionality, and its easy enough
to create an interface and split the tickets back,however the only
problem I came across is identifying the original requesters/watchers
for each ticket, to do this cleanly the merge function need to be
modified so it store the original People list for each ticket.
Roy
Brett Sheffield wrote:
Dmitriy Yermakov пишет:
For example
[rt3]> select id,EffectiveId from Tickets where id =6999;
+------+-------------+
| id | EffectiveId |
+------+-------------+
| 6999 | 6842 |
so, ticket #6999 merged into ticket #6842
for un-merge
[rt3]> update Tickets set EffectiveId=6999 where id=6999;
Thanks - that does the trick. I gather from your answer that there is
no way of doing this in the interface? I had assumed I had missed
something in the manual.
As this is a fairly easy mistake to make and it is not desirable to give
ordinary users access to the database, would it be useful for this
feature to be added to the interface? I note that all other forms of
linking tickets can be undone by "checking box to delete" in the links page.
_______________________________________________
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
Community help: http://wiki.bestpractical.com
Commercial support: [EMAIL PROTECTED]
Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
Buy a copy at http://rtbook.bestpractical.com
_______________________________________________
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
Community help: http://wiki.bestpractical.com
Commercial support: [EMAIL PROTECTED]
Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
Buy a copy at http://rtbook.bestpractical.com
