Known Error - Revision history

User at 22:11, 5 January 2023

2023-01-05T22:11:10Z

User at 14:43, 23 November 2022

2022-11-23T14:43:11Z

User: The LinkTitles extension automatically added links to existing pages (https://github.com/bovender/LinkTitles).

2021-02-06T16:47:22Z

The LinkTitles extension automatically added links to existing pages (https://github.com/bovender/LinkTitles).

User at 18:13, 29 January 2021

2021-01-29T18:13:54Z

User at 18:13, 29 January 2021

2021-01-29T18:13:07Z

User at 17:44, 29 January 2021

2021-01-29T17:44:38Z

User at 17:37, 29 January 2021

2021-01-29T17:37:05Z

User at 15:35, 29 January 2021

2021-01-29T15:35:53Z

User: Created page with "A '''Known Error''' is a problem that has a documented root cause and a Workaround. Known Errors are managed throughout their lifecycle by the ITIL Problem Management|Pr..."

2021-01-29T15:31:02Z

Created page with "A '''Known Error''' is a problem that has a documented root cause and a Workaround. Known Errors are managed throughout their lifecycle by the ITIL Problem Management|Pr..."

New page

A '''Known Error''' is a problem that has a documented root cause and a [[Workaround]]. Known Errors are managed throughout their lifecycle by the [[ITIL Problem Management|Problem Management]] process. The details of each Known Error are recorded in a [[Known Error Record]] stored in the [[Known Error Database (KEDB)]].<ref>Definition - What Does Known Error Mean? [https://wiki.en.it-processmaps.com/index.php/Problem_Management#:~:text=A%20Known%20Error%20is%20a,Known%20Error%20Database%20(KEDB) IT ProcessMaps]</ref>

Known error comprises [[Software|software]] bugs that have yet to be fixed, but have a known [[Root Cause|root cause]] and either have little disruptive impact on the end user or a known work around. Tested systems are often described as "free from known error" in recognition that complex systems cannot be proven to be error free. In [[IT Operations (Information Technology Operations)|IT Operations]] known errors may be logged in a system's Known Error Database (KEDB) which is then used to prioritize changes and to develop customer support reference information where a work around exists.<ref>What is Known Error [https://en.wikipedia.org/wiki/Known_error Wikipedia]</ref>

Officially, Known Errors belong to Problem Management, but it’s not unusual for Service Desk to resolve an incident with a permanent solution, or find a workaround and create a Known Error record. The aim of the Problem Management is to find a root cause of one or more incidents. Problems are created because the root cause (the real cause of the incident) and its resolution need to be identified. The result of the problem investigation and diagnosis is identification of the root cause of the problem, and a workaround (temporary fix) or (final) resolution. These are valuable pieces of information and need to be recorded – so, a Known Error is created.<ref>Explaining Known Error [https://advisera.com/20000academy/blog/2014/02/04/known-errors-repetitio-est-mater-studiorum-case/ Branimir Valentic]</ref>

[[File:Known Error.jpg|400px|Known Error]]<br />
source: Advisera

@@ Line 1: / Line 1: @@
-A '''Known Error''' is a problem that has a documented root cause and a [[Workaround]]. Known Errors are managed throughout their lifecycle by the [[ITIL Problem Management|Problem Management]] [[process]]. The details of each Known Error are recorded in a [[Known Error Record]] stored in the [[Known Error Database (KEDB)]].<ref>Definition - What Does Known Error Mean? [https://wiki.en.it-processmaps.com/index.php/Problem_Management#:~:text=A%20Known%20Error%20is%20a,Known%20Error%20Database%20(KEDB) IT ProcessMaps]</ref>
+== What is a Known Error? ==
-Known error comprises [[Software|software]] bugs that have yet to be fixed, but have a known [[Root Cause|root cause]] and either have little disruptive impact on the end user or a known work around. Tested systems are often described as "free from known error" in recognition that complex systems cannot be proven to be error free. In [[IT Operations (Information Technology Operations)|IT Operations]] known errors may be logged in a [[system]]'s Known Error Database (KEDB) which is then used to prioritize changes and to develop [[customer]] support reference information where a work around exists.<ref>What is Known Error [https://en.wikipedia.org/wiki/Known_error Wikipedia]</ref>
+A '''Known Error''' is a problem that has a documented root cause and a [[Workaround]]. Known Errors are managed throughout their lifecycle by the [[ITIL Problem Management|Problem Management]] process. The details of each Known Error are recorded in a [[Known Error Record]] stored in the [[Known Error Database (KEDB)]].<ref>Definition - What Does Known Error Mean? [https://wiki.en.it-processmaps.com/index.php/Problem_Management#:~:text=A%20Known%20Error%20is%20a,Known%20Error%20Database%20(KEDB) IT ProcessMaps]</ref>
-Officially, Known Errors belong to Problem [[Management]], but it’s not unusual for [[Service]] Desk to resolve an incident with a permanent solution, or find a workaround and create a Known Error record.  The aim of the Problem Management is to find a root cause of one or more incidents. Problems are created because the root cause (the real cause of the incident) and its resolution need to be identified. The result of the problem investigation and diagnosis is identification of the root cause of the problem, and a workaround (temporary fix) or (final) resolution. These are valuable pieces of information and need to be recorded – so, a Known Error is created.<ref>Explaining Known Error [https://advisera.com/20000academy/blog/2014/02/04/known-errors-repetitio-est-mater-studiorum-case/ Branimir Valentic]</ref>
+Known error comprises software bugs that have yet to be fixed, but have a known [[Root Cause|root cause]] and either have a little disruptive impact on the end user or a known workaround. Tested systems are often described as "free from known error" in recognition that complex systems cannot be proven to be error-free. In [[IT Operations (Information Technology Operations)|IT Operations]] known errors may be logged in a system's Known Error Database (KEDB) which is then used to prioritize changes and to develop customer support reference information where a work around exists.<ref>What is Known Error [https://en.wikipedia.org/wiki/Known_error Wikipedia]</ref>
-Known Errors typically have two parts. The first of these is the description of the Known Error itself, showing users or [[product]] modules and versions affected. The second is the Workaround and/or Change:
+Officially, Known Errors belong to Problem Management, but it’s not unusual for Service Desk to resolve an incident with a permanent solution, or find a workaround and create a Known Error record.  The aim of the Problem Management is to find a root cause of one or more incidents. Problems are created because the root cause (the real cause of the incident) and its resolution need to be identified. The result of the problem investigation and diagnosis is identification of the root cause of the problem, and a workaround (temporary fix) or (final) resolution. These are valuable pieces of information and need to be recorded – so, a Known Error is created.<ref>Explaining Known Error [https://advisera.com/20000academy/blog/2014/02/04/known-errors-repetitio-est-mater-studiorum-case/ Branimir Valentic]</ref>
 *Workaround – a way to bypass the fault you've previous described that can be used by Customers.
 *Change – to resolve the underlying Problem.
@@ Line 30: / Line 32: @@
 *Is closed at the end of its life cycle:
 **It will either disappear from the known error knowledge base when the malfunctioning no longer occurs. In this case, linked incidents will automatically be updated.
-**Or it will remain in the known error knowledge base if the workaround solution is unable to solve the malfunctioning permanently but no further investigations will be conducted.<ref>Explaining Known Error [https://wiki.easyvista.com/xwiki/bin/view/Documentation/Known+Error#:~:text=See%20Life%20Cycle-,Examples,to%20a%20software%20version%20release Easy Vista]</ref>
+**Or it will remain in the known error knowledge base if the workaround solution is unable to solve the malfunctioning permanently but no further investigations will be conducted.<ref>[https://wiki.easyvista.com/xwiki/bin/view/Documentation/Known+Error Explaining Known Error -Easy Vista]</ref>
 '''References'''
 <references/>

@@ Line 1: / Line 1: @@
 A '''Known Error''' is a problem that has a documented root cause and a [[Workaround]]. Known Errors are managed throughout their lifecycle by the [[ITIL Problem Management|Problem Management]] [[process]]. The details of each Known Error are recorded in a [[Known Error Record]] stored in the [[Known Error Database (KEDB)]].<ref>Definition - What Does Known Error Mean? [https://wiki.en.it-processmaps.com/index.php/Problem_Management#:~:text=A%20Known%20Error%20is%20a,Known%20Error%20Database%20(KEDB) IT ProcessMaps]</ref>
-Known error comprises [[Software|software]] bugs that have yet to be fixed, but have a known [[Root Cause|root cause]] and either have little disruptive [[impact]] on the end user or a known work around. Tested systems are often described as "free from known error" in recognition that complex systems cannot be proven to be error free. In [[IT Operations (Information Technology Operations)|IT Operations]] known errors may be logged in a [[system]]'s Known Error Database (KEDB) which is then used to prioritize changes and to develop [[customer]] support reference information where a work around exists.<ref>What is Known Error [https://en.wikipedia.org/wiki/Known_error Wikipedia]</ref>
+Known error comprises [[Software|software]] bugs that have yet to be fixed, but have a known [[Root Cause|root cause]] and either have little disruptive impact on the end user or a known work around. Tested systems are often described as "free from known error" in recognition that complex systems cannot be proven to be error free. In [[IT Operations (Information Technology Operations)|IT Operations]] known errors may be logged in a [[system]]'s Known Error Database (KEDB) which is then used to prioritize changes and to develop [[customer]] support reference information where a work around exists.<ref>What is Known Error [https://en.wikipedia.org/wiki/Known_error Wikipedia]</ref>
 Officially, Known Errors belong to Problem [[Management]], but it’s not unusual for [[Service]] Desk to resolve an incident with a permanent solution, or find a workaround and create a Known Error record.  The aim of the Problem Management is to find a root cause of one or more incidents. Problems are created because the root cause (the real cause of the incident) and its resolution need to be identified. The result of the problem investigation and diagnosis is identification of the root cause of the problem, and a workaround (temporary fix) or (final) resolution. These are valuable pieces of information and need to be recorded – so, a Known Error is created.<ref>Explaining Known Error [https://advisera.com/20000academy/blog/2014/02/04/known-errors-repetitio-est-mater-studiorum-case/ Branimir Valentic]</ref>

@@ Line 1: / Line 1: @@
-A '''Known Error''' is a problem that has a documented root cause and a [[Workaround]]. Known Errors are managed throughout their lifecycle by the [[ITIL Problem Management|Problem Management]] process. The details of each Known Error are recorded in a [[Known Error Record]] stored in the [[Known Error Database (KEDB)]].<ref>Definition - What Does Known Error Mean? [https://wiki.en.it-processmaps.com/index.php/Problem_Management#:~:text=A%20Known%20Error%20is%20a,Known%20Error%20Database%20(KEDB) IT ProcessMaps]</ref>
+A '''Known Error''' is a problem that has a documented root cause and a [[Workaround]]. Known Errors are managed throughout their lifecycle by the [[ITIL Problem Management|Problem Management]] [[process]]. The details of each Known Error are recorded in a [[Known Error Record]] stored in the [[Known Error Database (KEDB)]].<ref>Definition - What Does Known Error Mean? [https://wiki.en.it-processmaps.com/index.php/Problem_Management#:~:text=A%20Known%20Error%20is%20a,Known%20Error%20Database%20(KEDB) IT ProcessMaps]</ref>
-Known error comprises [[Software|software]] bugs that have yet to be fixed, but have a known [[Root Cause|root cause]] and either have little disruptive impact on the end user or a known work around. Tested systems are often described as "free from known error" in recognition that complex systems cannot be proven to be error free. In [[IT Operations (Information Technology Operations)|IT Operations]] known errors may be logged in a system's Known Error Database (KEDB) which is then used to prioritize changes and to develop customer support reference information where a work around exists.<ref>What is Known Error [https://en.wikipedia.org/wiki/Known_error Wikipedia]</ref>
+Known error comprises [[Software|software]] bugs that have yet to be fixed, but have a known [[Root Cause|root cause]] and either have little disruptive [[impact]] on the end user or a known work around. Tested systems are often described as "free from known error" in recognition that complex systems cannot be proven to be error free. In [[IT Operations (Information Technology Operations)|IT Operations]] known errors may be logged in a [[system]]'s Known Error Database (KEDB) which is then used to prioritize changes and to develop [[customer]] support reference information where a work around exists.<ref>What is Known Error [https://en.wikipedia.org/wiki/Known_error Wikipedia]</ref>
-Officially, Known Errors belong to Problem Management, but it’s not unusual for Service Desk to resolve an incident with a permanent solution, or find a workaround and create a Known Error record.  The aim of the Problem Management is to find a root cause of one or more incidents. Problems are created because the root cause (the real cause of the incident) and its resolution need to be identified. The result of the problem investigation and diagnosis is identification of the root cause of the problem, and a workaround (temporary fix) or (final) resolution. These are valuable pieces of information and need to be recorded – so, a Known Error is created.<ref>Explaining Known Error [https://advisera.com/20000academy/blog/2014/02/04/known-errors-repetitio-est-mater-studiorum-case/ Branimir Valentic]</ref>
+Officially, Known Errors belong to Problem [[Management]], but it’s not unusual for [[Service]] Desk to resolve an incident with a permanent solution, or find a workaround and create a Known Error record.  The aim of the Problem Management is to find a root cause of one or more incidents. Problems are created because the root cause (the real cause of the incident) and its resolution need to be identified. The result of the problem investigation and diagnosis is identification of the root cause of the problem, and a workaround (temporary fix) or (final) resolution. These are valuable pieces of information and need to be recorded – so, a Known Error is created.<ref>Explaining Known Error [https://advisera.com/20000academy/blog/2014/02/04/known-errors-repetitio-est-mater-studiorum-case/ Branimir Valentic]</ref>
-Known Errors typically have two parts. The first of these is the description of the Known Error itself, showing users or product modules and versions affected. The second is the Workaround and/or Change:
+Known Errors typically have two parts. The first of these is the description of the Known Error itself, showing users or [[product]] modules and versions affected. The second is the Workaround and/or Change:
 *Workaround – a way to bypass the fault you've previous described that can be used by Customers.
 *Change – to resolve the underlying Problem.

← Older revision		Revision as of 18:13, 29 January 2021
Line 31:		Line 31:
	**It will either disappear from the known error knowledge base when the malfunctioning no longer occurs. In this case, linked incidents will automatically be updated.		**It will either disappear from the known error knowledge base when the malfunctioning no longer occurs. In this case, linked incidents will automatically be updated.
	**Or it will remain in the known error knowledge base if the workaround solution is unable to solve the malfunctioning permanently but no further investigations will be conducted.<ref>Explaining Known Error [https://wiki.easyvista.com/xwiki/bin/view/Documentation/Known+Error#:~:text=See%20Life%20Cycle-,Examples,to%20a%20software%20version%20release Easy Vista]</ref>		**Or it will remain in the known error knowledge base if the workaround solution is unable to solve the malfunctioning permanently but no further investigations will be conducted.<ref>Explaining Known Error [https://wiki.easyvista.com/xwiki/bin/view/Documentation/Known+Error#:~:text=See%20Life%20Cycle-,Examples,to%20a%20software%20version%20release Easy Vista]</ref>
		+
		+
		+	'''References'''
		+	<references/>

← Older revision		Revision as of 18:13, 29 January 2021
Line 11:		Line 11:


−	[[File:Known Error.jpg\|~~400px~~\|Known Error]]<br />	+	[[File:Known Error.jpg\|500px\|Known Error]]<br />
	source: Advisera		source: Advisera
		+
		+
		+	A known error describes a workaround solution that solves a malfunctioning temporarily or permanently. It is usually created after the occurrence of a problem that causes incidents. However, it can also be created upstream.
		+	Each known error:
		+	*Is created:
		+	**Via an incident or problem.
		+	**Individually to avoid potential incidents occurring.
		+	*Is systematically saved in the known error knowledge base and can be associated with keywords to facilitate searches.
		+	*Has a status so its progress can be monitored.
		+	*Can be linked to a parent error. This enables in-depth analysis of the error through more specific questions/responses at each level. Open url.png See the example.
		+	*Can be associated with a type, used to group errors by theme to make searching the knowledge base easier.
		+	*Can be associated with a category from the incident catalog, used in the ticket to display:
		+	**Only known errors defined for the same category as the incident.
		+	**All known errors if the category of the incident is not specified.
		+	*Can be communicated in a news article.
		+	*Is closed at the end of its life cycle:
		+	**It will either disappear from the known error knowledge base when the malfunctioning no longer occurs. In this case, linked incidents will automatically be updated.
		+	**Or it will remain in the known error knowledge base if the workaround solution is unable to solve the malfunctioning permanently but no further investigations will be conducted.<ref>Explaining Known Error [https://wiki.easyvista.com/xwiki/bin/view/Documentation/Known+Error#:~:text=See%20Life%20Cycle-,Examples,to%20a%20software%20version%20release Easy Vista]</ref>

← Older revision		Revision as of 17:44, 29 January 2021
Line 1:		Line 1:
−	A '''Known Error''' is a problem that has a documented root cause and a [[Workaround]]. Known Errors are managed throughout their lifecycle by the [[ITIL Problem Management\|Problem Management]] process. The details of each Known Error are recorded in a Known Error Record stored in the [[Known Error Database (KEDB)]].<ref>Definition - What Does Known Error Mean? [https://wiki.en.it-processmaps.com/index.php/Problem_Management#:~:text=A%20Known%20Error%20is%20a,Known%20Error%20Database%20(KEDB) IT ProcessMaps]</ref>	+	A '''Known Error''' is a problem that has a documented root cause and a [[Workaround]]. Known Errors are managed throughout their lifecycle by the [[ITIL Problem Management\|Problem Management]] process. The details of each Known Error are recorded in a [[Known Error Record]] stored in the [[Known Error Database (KEDB)]].<ref>Definition - What Does Known Error Mean? [https://wiki.en.it-processmaps.com/index.php/Problem_Management#:~:text=A%20Known%20Error%20is%20a,Known%20Error%20Database%20(KEDB) IT ProcessMaps]</ref>

	Known error comprises [[Software\|software]] bugs that have yet to be fixed, but have a known [[Root Cause\|root cause]] and either have little disruptive impact on the end user or a known work around. Tested systems are often described as "free from known error" in recognition that complex systems cannot be proven to be error free. In [[IT Operations (Information Technology Operations)\|IT Operations]] known errors may be logged in a system's Known Error Database (KEDB) which is then used to prioritize changes and to develop customer support reference information where a work around exists.<ref>What is Known Error [https://en.wikipedia.org/wiki/Known_error Wikipedia]</ref>		Known error comprises [[Software\|software]] bugs that have yet to be fixed, but have a known [[Root Cause\|root cause]] and either have little disruptive impact on the end user or a known work around. Tested systems are often described as "free from known error" in recognition that complex systems cannot be proven to be error free. In [[IT Operations (Information Technology Operations)\|IT Operations]] known errors may be logged in a system's Known Error Database (KEDB) which is then used to prioritize changes and to develop customer support reference information where a work around exists.<ref>What is Known Error [https://en.wikipedia.org/wiki/Known_error Wikipedia]</ref>

← Older revision		Revision as of 17:37, 29 January 2021
Line 1:		Line 1:
−	A '''Known Error''' is a problem that has a documented root cause and a [[Workaround]]. Known Errors are managed throughout their lifecycle by the [[ITIL Problem Management\|Problem Management]] process. The details of each Known Error are recorded in a [[Known Error Record]] stored in the [[Known Error Database (KEDB)]].<ref>Definition - What Does Known Error Mean? [https://wiki.en.it-processmaps.com/index.php/Problem_Management#:~:text=A%20Known%20Error%20is%20a,Known%20Error%20Database%20(KEDB) IT ProcessMaps]</ref>	+	A '''Known Error''' is a problem that has a documented root cause and a [[Workaround]]. Known Errors are managed throughout their lifecycle by the [[ITIL Problem Management\|Problem Management]] process. The details of each Known Error are recorded in a Known Error Record stored in the [[Known Error Database (KEDB)]].<ref>Definition - What Does Known Error Mean? [https://wiki.en.it-processmaps.com/index.php/Problem_Management#:~:text=A%20Known%20Error%20is%20a,Known%20Error%20Database%20(KEDB) IT ProcessMaps]</ref>

	Known error comprises [[Software\|software]] bugs that have yet to be fixed, but have a known [[Root Cause\|root cause]] and either have little disruptive impact on the end user or a known work around. Tested systems are often described as "free from known error" in recognition that complex systems cannot be proven to be error free. In [[IT Operations (Information Technology Operations)\|IT Operations]] known errors may be logged in a system's Known Error Database (KEDB) which is then used to prioritize changes and to develop customer support reference information where a work around exists.<ref>What is Known Error [https://en.wikipedia.org/wiki/Known_error Wikipedia]</ref>		Known error comprises [[Software\|software]] bugs that have yet to be fixed, but have a known [[Root Cause\|root cause]] and either have little disruptive impact on the end user or a known work around. Tested systems are often described as "free from known error" in recognition that complex systems cannot be proven to be error free. In [[IT Operations (Information Technology Operations)\|IT Operations]] known errors may be logged in a system's Known Error Database (KEDB) which is then used to prioritize changes and to develop customer support reference information where a work around exists.<ref>What is Known Error [https://en.wikipedia.org/wiki/Known_error Wikipedia]</ref>

@@ Line 4: / Line 4: @@
 Officially, Known Errors belong to Problem Management, but it’s not unusual for Service Desk to resolve an incident with a permanent solution, or find a workaround and create a Known Error record.  The aim of the Problem Management is to find a root cause of one or more incidents. Problems are created because the root cause (the real cause of the incident) and its resolution need to be identified. The result of the problem investigation and diagnosis is identification of the root cause of the problem, and a workaround (temporary fix) or (final) resolution. These are valuable pieces of information and need to be recorded – so, a Known Error is created.<ref>Explaining Known Error [https://advisera.com/20000academy/blog/2014/02/04/known-errors-repetitio-est-mater-studiorum-case/ Branimir Valentic]</ref>
 [[File:Known Error.jpg|400px|Known Error]]<br />
 source: Advisera