Template:Handling errors - Revision history

Joel at 06:52, 25 June 2018

2018-06-25T06:52:33Z

← Older revision		Revision as of 06:52, 25 June 2018
Line 6:		Line 6:
	#Support MUST always provide full screenshots of all the steps required to replicate the error, as this will help identify the cause of the error much quicker.		#Support MUST always provide full screenshots of all the steps required to replicate the error, as this will help identify the cause of the error much quicker.
	#When sending screenshots of the issue to your manager, the top-left of the browser MUST be visible so that it is clear which browser, URL and database is used.		#When sending screenshots of the issue to your manager, the top-left of the browser MUST be visible so that it is clear which browser, URL and database is used.
	#Ensure that script errors (if any) are included in the screenshots.		#Ensure that script errors (if any) are included in the screenshots. Include every detail available regarding the script error, for example: script name, line number etc.
	#Support MUST report the error to support team by email to keep a record of all errors in ~~neosys~~. Support team looks good when errors are spotted and fixed pro actively. Do not ignore the error for any reason.		#Support MUST report the error to support team by email to keep a record of all errors in NEOSYS. Support team looks good when errors are spotted and fixed pro actively. Do not ignore the error for any reason.
	#When requesting the programmer to fix the issue, explain WHAT has to be fixed and HOW it has to be fixed. Refer to [[Procedures#Handling_requests_to_create_a_new_feature_or_modifying_existing_features\| Handling request to create a new feature or modifying existing features]]		#When requesting the programmer to fix the issue, explain WHAT has to be fixed and HOW it has to be fixed. Refer to [[Procedures#Handling_requests_to_create_a_new_feature_or_modifying_existing_features\| Handling request to create a new feature or modifying existing features]]
	#The most important step when solving any problem is Future Prevention. eg. add the solution to wiki, so that support spends lesser time fixing the problem in future.		#The most important step when solving any problem is Future Prevention. eg. add the solution to wiki, so that support spends lesser time fixing the problem in future.

Arvind at 13:44, 4 February 2018

2018-02-04T13:44:44Z

← Older revision		Revision as of 13:44, 4 February 2018
Line 3:		Line 3:
	#If there is no immediate fix for the error, try to find and provide a temporary workaround, which the client can use until the error is fixed.		#If there is no immediate fix for the error, try to find and provide a temporary workaround, which the client can use until the error is fixed.
	#If the error is new, do a thorough investigation (eg. check NEOSYS logs) and try to find a solution for the error.		#If the error is new, do a thorough investigation (eg. check NEOSYS logs) and try to find a solution for the error.
	#If you still cannot find a fix for the error, then escalate the issue to your manager with an explanation of the issue ~~and the exact steps to reproduce the error~~.		#If you still cannot find a fix for the error, then escalate the issue to your manager with an explanation of the issue.
	#~~Steps and~~ screenshots to replicate an error ~~MUST always be provided when reporting the issue~~ as ~~it is~~ the ~~most basic step in fixing~~ the error~~. Support MUST always provide complete and accurate steps~~.		#Support MUST always provide full screenshots of all the steps required to replicate the error, as this will help identify the cause of the error much quicker.
	#When sending screenshots of the issue to your manager, the top-left of the browser MUST be visible so that it is clear which browser, URL and database is used.		#When sending screenshots of the issue to your manager, the top-left of the browser MUST be visible so that it is clear which browser, URL and database is used.
	#Ensure that script errors (if any) are included in the screenshots.		#Ensure that script errors (if any) are included in the screenshots.

Joel at 10:34, 25 January 2018

2018-01-25T10:34:51Z

← Older revision		Revision as of 10:34, 25 January 2018
Line 1:		Line 1:
	#Replicate the error on all browsers after ensuring that the browsers have script error notifications enabled.		#Replicate the error on all browsers after ensuring that the browsers have script error notifications enabled.
	#Check in all the wikis for a solution.		#Check in all the wikis for a solution.
	#If there is no immediate fix for the ~~issue~~, try to find and provide a temporary workaround ~~for the issue~~, which the client can use until the error is fixed.		#If there is no immediate fix for the error, try to find and provide a temporary workaround, which the client can use until the error is fixed.
	#If the ~~issue~~ is new, do a thorough investigation (eg. check NEOSYS logs) and try to find a solution for the ~~issue~~.		#If the error is new, do a thorough investigation (eg. check NEOSYS logs) and try to find a solution for the error.
	#If you still cannot find a fix for the ~~issue~~, then escalate the issue to your manager with an explanation of the issue and the exact steps to reproduce the error.		#If you still cannot find a fix for the error, then escalate the issue to your manager with an explanation of the issue and the exact steps to reproduce the error.
			#Steps and screenshots to replicate an error MUST always be provided when reporting the issue as it is the most basic step in fixing the error. Support MUST always provide complete and accurate steps.
	#When sending screenshots of the issue to your manager, the top-left of the browser MUST be visible so that it is clear which browser, URL and database is used.		#When sending screenshots of the issue to your manager, the top-left of the browser MUST be visible so that it is clear which browser, URL and database is used.
	#Ensure that script errors (if any) are included in the screenshots.		#Ensure that script errors (if any) are included in the screenshots.

Priyanka at 06:31, 11 February 2016

2016-02-11T06:31:49Z

← Older revision		Revision as of 06:31, 11 February 2016
Line 6:		Line 6:
	#When sending screenshots of the issue to your manager, the top-left of the browser MUST be visible so that it is clear which browser, URL and database is used.		#When sending screenshots of the issue to your manager, the top-left of the browser MUST be visible so that it is clear which browser, URL and database is used.
	#Ensure that script errors (if any) are included in the screenshots.		#Ensure that script errors (if any) are included in the screenshots.
	#~~Report~~ the error to support team~~, do~~ not ignore the error ~~and move forward~~.		#Support MUST report the error to support team by email to keep a record of all errors in neosys. Support team looks good when errors are spotted and fixed pro actively. Do not ignore the error for any reason.
	#When requesting the programmer to fix the issue, explain WHAT has to be fixed and HOW it has to be fixed. Refer to [[Procedures#Handling_requests_to_create_a_new_feature_or_modifying_existing_features\| ~~Handeling~~ request to create a new feature or ~~modiying~~ existing features]]		#When requesting the programmer to fix the issue, explain WHAT has to be fixed and HOW it has to be fixed. Refer to [[Procedures#Handling_requests_to_create_a_new_feature_or_modifying_existing_features\| Handling request to create a new feature or modifying existing features]]
	#The most important step when solving any problem is Future Prevention. eg. add the solution to wiki, so that support spends lesser time fixing the problem in future.		#The most important step when solving any problem is Future Prevention. eg. add the solution to wiki, so that support spends lesser time fixing the problem in future.

Priyanka: Created page with "#Replicate the error on all browsers after ensuring that the browsers have script error notifications enabled. #Check in all the wikis for a solution. #If there is no immediat..."

2016-02-11T06:23:17Z

Created page with "#Replicate the error on all browsers after ensuring that the browsers have script error notifications enabled. #Check in all the wikis for a solution. #If there is no immediat..."

New page

#Replicate the error on all browsers after ensuring that the browsers have script error notifications enabled.
#Check in all the wikis for a solution.
#If there is no immediate fix for the issue, try to find and provide a temporary workaround for the issue, which the client can use until the error is fixed.
#If the issue is new, do a thorough investigation (eg. check NEOSYS logs) and try to find a solution for the issue.
#If you still cannot find a fix for the issue, then escalate the issue to your manager with an explanation of the issue and the exact steps to reproduce the error.
#When sending screenshots of the issue to your manager, the top-left of the browser MUST be visible so that it is clear which browser, URL and database is used.
#Ensure that script errors (if any) are included in the screenshots.
#Report the error to support team, do not ignore the error and move forward.
#When requesting the programmer to fix the issue, explain WHAT has to be fixed and HOW it has to be fixed. Refer to [[Procedures#Handling_requests_to_create_a_new_feature_or_modifying_existing_features| Handeling request to create a new feature or modiying existing features]]
#The most important step when solving any problem is Future Prevention. eg. add the solution to wiki, so that support spends lesser time fixing the problem in future.