Some background information
It was around 1990. Registration of all kinds of things happened online in the daytime, but the (financial) processing of all that took place outside of working hourse e in the form of batch processing of all the new and modified data.
This process was important enough to have us programmers standby to be able to act when somathing went wrong, and this little application was intended to help us record these action so that we might look back on them later in case of similar accidents.
If I remember correctly it consisted of a list and three detail screens: the list was meant to present an overview of the incidents; the first detail screen was for describing the problem situation; the second to describe the actions taken to immediately resolve it and the third could be used to describe actions that would have to be taken afterwards, if any.
Solutions could vary from "error in software fixed; resumed batch" to "temporary bypass in program; resumed batch" to "batch canceled; further analysis in the morning" and the list could be sorted in various ways, for instance to put the situations that required a follow-up to be presented first.
All information was meant to be entered at the time of the incident and not to be touched afterwards, except maybe to add that the follow-up actions had be done, so it wasn't really an issue tracker.