Ticket Merge - Revision history

Dina at 13:50, 8 July 2020

2020-07-08T13:50:58Z

← Older revision		Revision as of 13:50, 8 July 2020
Line 5:		Line 5:

	=Performing Ticket Merge=		=Performing Ticket Merge=
	Before performing the Ticket Merge, it is advised to make sure you have a recent backup of your ~~CommitCRM~~ database.		Before performing the Ticket Merge, it is advised to make sure you have a recent backup of your RangerMSP database.

	To activate the Ticket Merge option:		To activate the Ticket Merge option:
	# Close all internal Windows within ~~CommitCRM~~. Then go to ''Tools > Data Tools > Ticket Merge''.		# Close all internal Windows within RangerMSP. Then go to ''Tools > Data Tools > Ticket Merge''.
	# The following window opens: <br>[[File:Ticket_merge_window.gif]]<br>In this window, choose the redundant and master Tickets for the merge operation. Note that the redundant Ticket will be deleted at the end of this operation. Use the following fields:		# The following window opens: <br>[[File:Ticket_merge_window.gif]]<br>In this window, choose the redundant and master Tickets for the merge operation. Note that the redundant Ticket will be deleted at the end of this operation. Use the following fields:
	## Merge From - Redundant Ticket - To be merged and then deleted. <br>Linked Data will be moved to the Master Ticket and the Ticket details will be added to the History tab of the Master Ticket. The Account will be deleted.		## Merge From - Redundant Ticket - To be merged and then deleted. <br>Linked Data will be moved to the Master Ticket and the Ticket details will be added to the History tab of the Master Ticket. The Account will be deleted.

Sheli: /* Performing Ticket Merge */

2011-08-05T11:36:32Z

Performing Ticket Merge

← Older revision		Revision as of 11:36, 5 August 2011
Line 5:		Line 5:

	=Performing Ticket Merge=		=Performing Ticket Merge=
	The Ticket Merge action performs a massive database update transaction that cannot be undone, and therefore it is advised to perform it carefully. It also requires special privilege to make sure not anyone can perform this action.		Before performing the Ticket Merge, it is advised to make sure you have a recent backup of your CommitCRM database.

	Before performing the Ticket Merge, it is advised to ~~perform~~ a backup your ~~entire~~ CommitCRM database.

	To activate the Ticket Merge option:		To activate the Ticket Merge option:
	# Close all internal Windows within CommitCRM. Then go to ''Tools > Data Tools > Ticket Merge''.		# Close all internal Windows within CommitCRM. Then go to ''Tools > Data Tools > Ticket Merge''.
	# The following window opens: <br>[[File:Ticket_merge_window.gif]]		# The following window opens: <br>[[File:Ticket_merge_window.gif]]<br>In this window, choose the redundant and master Tickets for the merge operation. Note that the redundant Ticket will be deleted at the end of this operation. Use the following fields:
	In this window, choose the redundant and master Tickets for the merge operation. Note that the redundant Ticket will be deleted at the end of this operation. Use the following fields:
	## Merge From - Redundant Ticket - To be merged and then deleted. <br>Linked Data will be moved to the Master Ticket and the Ticket details will be added to the History tab of the Master Ticket. The Account will be deleted.		## Merge From - Redundant Ticket - To be merged and then deleted. <br>Linked Data will be moved to the Master Ticket and the Ticket details will be added to the History tab of the Master Ticket. The Account will be deleted.
	## Merge To - Master Ticket - Receives all data from the redundant Ticket.		## Merge To - Master Ticket - Receives all data from the redundant Ticket.

Sheli at 09:43, 5 August 2011

2011-08-05T09:43:43Z

← Older revision		Revision as of 09:43, 5 August 2011
Line 1:		Line 1:
	''* Note: This feature is available only when using CommitCRM version 5.6 *
	''


	=Introduction=		=Introduction=
	The Ticket Merge utility helps you merge two Tickets into one. The merge operation copies the data from one Ticket to the other (the Master Ticket) and deletes the redundant Ticket.		The Ticket Merge utility helps you merge two Tickets into one. The merge operation copies the data from one Ticket to the other (the Master Ticket) and deletes the redundant Ticket.

Sheli: /* Performing Ticket Merge */

2011-08-04T11:48:45Z

Performing Ticket Merge

← Older revision		Revision as of 11:48, 4 August 2011
Line 11:		Line 11:
	The Ticket Merge action performs a massive database update transaction that cannot be undone, and therefore it is advised to perform it carefully. It also requires special privilege to make sure not anyone can perform this action.		The Ticket Merge action performs a massive database update transaction that cannot be undone, and therefore it is advised to perform it carefully. It also requires special privilege to make sure not anyone can perform this action.

	Before performing the Ticket Merge:		Before performing the Ticket Merge, it is advised to perform a backup your entire CommitCRM database.

	* Verify that no one on your network is ~~running CommitCRM.~~
	* Stop CommitWebInterface and CommitServer services on your server (if installed).
	* Backup your entire CommitCRM database ~~(do not proceed without a backup!)~~.


	To activate the Ticket Merge option:		To activate the Ticket Merge option:
Line 26:		Line 21:


	~~Notes~~:		''Note: Only Tickets which are linked to the same Account can be merged. If you want to merge all Tickets to a single Account, see Account Merge.''
	# Only Tickets which are linked to the same Account can be merged. If you want to merge all Tickets to a single Account, see Account Merge.
	# The Ticket Merge includes massive database transaction. In case of an error you may be required to restore the database from a backup. In such cases an appropriate message will be displayed. Make sure to backup your database before performing the Ticket Merge.
	# When using Commit SQL Database the transaction will be aborted before performed if there is a problem, and the user will probably not be required to restore. Nevertheless, it is advised to perform the backup in any case.

	=Privileges=		=Privileges=

Sheli at 11:01, 3 August 2011

2011-08-03T11:01:10Z

← Older revision		Revision as of 11:01, 3 August 2011
Line 1:		Line 1:
	''* Note: This feature is available only when using CommitCRM version 5.6 ~~which is currently in beta~~ *		''* Note: This feature is available only when using CommitCRM version 5.6 *
	''		''

Line 38:		Line 38:
	To allow employees to perform the Ticket Merge, use the following privilege:		To allow employees to perform the Ticket Merge, use the following privilege:

			[[File:Ticket_merge_priv.gif]]

	Note:		Note:

Sheli at 19:12, 31 July 2011

2011-07-31T19:12:44Z

← Older revision		Revision as of 19:12, 31 July 2011
Line 1:		Line 1:
			''* Note: This feature is available only when using CommitCRM version 5.6 which is currently in beta *
			''


	=Introduction=		=Introduction=
	The Ticket Merge utility helps you merge two Tickets into one. The merge operation copies the data from one Ticket to the other (the Master Ticket) and deletes the redundant Ticket.		The Ticket Merge utility helps you merge two Tickets into one. The merge operation copies the data from one Ticket to the other (the Master Ticket) and deletes the redundant Ticket.

Sheli at 19:11, 31 July 2011

2011-07-31T19:11:44Z

← Older revision		Revision as of 19:11, 31 July 2011
Line 27:		Line 27:
	# When using Commit SQL Database the transaction will be aborted before performed if there is a problem, and the user will probably not be required to restore. Nevertheless, it is advised to perform the backup in any case.		# When using Commit SQL Database the transaction will be aborted before performed if there is a problem, and the user will probably not be required to restore. Nevertheless, it is advised to perform the backup in any case.

	=~~Privilege for Ticket Merge~~=		=Privileges=
	The Ticket Merge action performs a massive database update transaction that cannot be undone, and therefore should be performed carefully.		The Ticket Merge action performs a massive database update transaction that cannot be undone, and therefore should be performed carefully.

Sheli: /* See Also */

2011-07-31T19:11:16Z

Sheli: Created page with '=Introduction= The Ticket Merge utility helps you merge two Tickets into one. The merge operation copies the data from one Ticket to the other (the Master Ticket) and deletes the…'

2011-07-31T19:10:30Z

Created page with '=Introduction= The Ticket Merge utility helps you merge two Tickets into one. The merge operation copies the data from one Ticket to the other (the Master Ticket) and deletes the…'

New page

=Introduction=
The Ticket Merge utility helps you merge two Tickets into one. The merge operation copies the data from one Ticket to the other (the Master Ticket) and deletes the redundant Ticket.
All data linked to the redundant Ticket will be moved to the Master Ticket. This includes Email Recipients, Charges, History Notes, Appointments, Tasks, Documents and Messages.
The redundant Ticket details, such as Status, Priority and Description, are not copied to the Master Ticket and only the Master Ticket details are kept. However, the details of the redundant are logged as an Audit History Note under the Master Ticket's History tab.

=Performing Ticket Merge=
The Ticket Merge action performs a massive database update transaction that cannot be undone, and therefore it is advised to perform it carefully. It also requires special privilege to make sure not anyone can perform this action.

Before performing the Ticket Merge:

* Verify that no one on your network is running CommitCRM.
* Stop CommitWebInterface and CommitServer services on your server (if installed).
* Backup your entire CommitCRM database (do not proceed without a backup!).

To activate the Ticket Merge option:
# Close all internal Windows within CommitCRM. Then go to ''Tools > Data Tools > Ticket Merge''.
# The following window opens: <br>[[File:Ticket_merge_window.gif]]
In this window, choose the redundant and master Tickets for the merge operation. Note that the redundant Ticket will be deleted at the end of this operation. Use the following fields:
## Merge From - Redundant Ticket - To be merged and then deleted. <br>Linked Data will be moved to the Master Ticket and the Ticket details will be added to the History tab of the Master Ticket. The Account will be deleted.
## Merge To - Master Ticket - Receives all data from the redundant Ticket.

Notes:
# Only Tickets which are linked to the same Account can be merged. If you want to merge all Tickets to a single Account, see Account Merge.
# The Ticket Merge includes massive database transaction. In case of an error you may be required to restore the database from a backup. In such cases an appropriate message will be displayed. Make sure to backup your database before performing the Ticket Merge.
# When using Commit SQL Database the transaction will be aborted before performed if there is a problem, and the user will probably not be required to restore. Nevertheless, it is advised to perform the backup in any case.

=Privilege for Ticket Merge=
The Ticket Merge action performs a massive database update transaction that cannot be undone, and therefore should be performed carefully.

Only employee users with specific privilege for this action can perform the Ticket Merge.

To allow employees to perform the Ticket Merge, use the following privilege:

Note:
In addition to the Ticket Merge privilege the user also needs the following privileges:
* '''Tickets''': allow Edit and Delete.
* '''Other Employees Tickets''': allow Edit and Delete if any of the Tickets involved is assigned to another employee.

=See Also=
* [[Ticket Management]]
* [[Ticket Lifecycle]]

← Older revision		Revision as of 19:11, 31 July 2011
Line 42:		Line 42:
	=See Also=		=See Also=
	* [[Ticket Management]]		* [[Ticket Management]]
	* [[Ticket Lifecycle]]		* [[Tickets\|Ticket Lifecycle]]