Check the incidents that are closed or canceled but still active #87
Conversation
…ign that the close_states are not set correctly on the incident table). This check can be done on any table, especially there where the State model was changed from OOTB or for custom extended tables. The problem with this kind of records is that they can influence the reports on active records on the respective table.
Iuliak
changed the title
|
@Iuliak Can you please add a description of the check to the readme file as part of this PR? |
|
Readme.md |
|
That content is good. It just needs to be added to the repository readme.md file under the appropriate category as another commit, with a heading as per the other entries 😃 |
…ctive check README.md Added the Check the incidents that are closed or canceled but still active check
|
Ah ok, done :) hopefully :D |
|
@Iuliak Great description of the check. Good job! Could you please move the description in the readme to the appropriate category section? The readme file has different sections for different categories of Instance Scan. I see the scan you created is under the Manageability category but the description in the readme was put under the User Experience category. |
Moved the Check for incidents closed and still active in the manageability Section
|
@niamccash yes, sorry .. I think its ok now. |
|
@Iuliak no apologies needed. It happens. Thank you for updating. Looks great! PR accepted! |
3 participants
A sign that the close_states are not set correctly on the incident table. This check can be done on any table, especially there where the State model was changed from OOTB or for custom extended tables. The problem with this kind of records is that they can influence the reports on active records on the respective table.
It is a simple table instance check.