Carry open issues forward with their current context
The open-issues handoff rereads the local log, follow-up plans and issue-to-work relationship index immediately before copying, saving to Project Passport or opening the contact form. That means the handoff includes the current issue state rather than an older prepared snapshot.
A follow-up plan is not an automatic maintenance deadline
For an open issue you may store an owner, the next concrete action and an optional target date. That date is entered by the user. ShelterMetric does not derive it from regulations and does not treat a passed target date as an automatically generated technical or legal status.
Why link completed work to a specific issue
A generic action record can describe work on any system without showing which earlier defect it addressed. The explicit relationship adds traceability: the original issue and the work records created against it remain connected, while ShelterMetric still makes no automatic conclusion that the defect has been eliminated.
One local log across the Ukrainian and English interfaces
The English and Ukrainian tools use the same browser-side operations-log storage. Switching language does not create a second copy of the facility history, and open/resolved states, follow-up plans and issue-linked work remain attached to the same issue IDs.
Why completed work does not automatically close a defect
A repair, inspection or service record does not by itself prove that a particular earlier issue has been eliminated. Even when a work record is directly linked to the issue, ShelterMetric changes the defect to resolved only when the user explicitly confirms that specific record.
What “resolved” means here
Resolved is a working state of one local record. It is not an automatically generated acceptance certificate, engineering conclusion or regulatory confirmation. If the facility requires a formal defect act, work certificate, test protocol or other controlled document, maintain that documentation separately.
Back up the browser-side history
The JSON backup preserves the record list, explicit issue lifecycle, issue-to-work relationships and follow-up plans. Older backups without the newer optional sections remain compatible.