Sorry dallas, but to make the input of reporting a KPI is the exact opposite of what you should do, there is talk of doing that around where I work, the problem with getting as many as you can into the system so it looks like you have a just culture is the system gets swamped and as no one can afford to sustain a healthy clearance rate, due to financial and commercial constraints mostly.
Closing the issues out in the correct manner to satisfy the person who put the issue in is the most imperative part of the process, if you don't close them and put the right process/equipment/people in place people get disillusioned and give up on the system and then you run the risk of missing the one that will stop the accident happen, which is even worse than not meeting the KPI.
Again a KPI was being muted for closure rates, but this is also unattainable and impracticable for all the reasons already stated.
You can also end up with open legacy issues and trust me you can get personnel to put all sorts into the system if you push them hard and long enough, and a lot of those should not and do not need to be put in as there are other methods of raising those through audits, suggestions boxes, GEMs etc, having a form of KPI to be met was attempted with Health and Safety kaizons and that was not very successful and is not utilized.
Back to the financial/commercial and dependency issues when it becomes to difficult it is either closed with some lame excuse or put onto the Risk Register or Hazard Log and that is also considered the issue sorted.