Skip to main content

Managing linked incidents on a rework

How to carry open incidents onto a rework and how linked incidents behave on both events.

When an event finishes with incidents still open, you can carry those incidents onto a rework so the outstanding work stays visible and traceable. The incident is not copied. It stays on the original event and is linked to the rework where it will be resolved.

This replaces the previous revisit flow. A rework keeps the event type of the event it was created from, and is identified by a rework marker rather than by a Revisit event type.

Linking incidents to a rework

There are two points where you can link open incidents to a rework.

When you approve the event

  1. Open the event and go to the Completion tab.

  2. Review the completion report and choose Not Completed.

  3. Choose to create a rework, and select which open incidents to carry over.

  4. Select a rework reason and confirm. The rework is created and the incidents are linked to it.

If you close the event without creating a rework, the incidents stay open on the original event.

From the Issues tab

  1. Open the event and go to the Issues tab.

  2. Select one or more incidents.

  3. Choose to link them to an existing event, or to a new event. Linking to a new event creates a rework.

  4. If you are creating a rework, select a rework reason and confirm.

Important

A rework reason is required. You cannot create a rework without selecting one.

How linked incidents behave

Once an incident is linked to a rework:

  • The originating event shows the incident with a Linked to reference pointing at the rework.

  • The rework shows the incident in a separate Linked section with a Linked from reference back to the original event.

  • Linked incidents are read-only on the rework. Only users with access to the original event can edit them.

  • You can open either event from the other, using the event name shown on the linked incident.

Each rework created from the same event is labeled with its sequence, R1, R2, R3, in the order the reworks were created. The sequence is shown on the event, not added to the event title.

Note

Lite users (installers) and vendors do not see whether an event is a rework, and do not see the rework reason. They still see the incidents assigned to them.

Changing or removing a link

You can move an incident to a different resolution event at any time. Open the linked incident from the Issues tab, remove the existing link, and link it to another event.

FAQ

What happens to incidents that are still open when I close a rework?

Incidents that are still open when you close a rework stay open. You can create another rework from that event and link the remaining incidents to it, which is then labeled as the next in the sequence.

Can I link the same incident to more than one rework?

An incident can only be linked to one resolution event at a time. To move it, remove the existing link first, then link it to the other event.

Do I still need to use the Revisit event type for a return visit?

You no longer need the Revisit event type for a return visit. A rework keeps the event type it was created from, and the rework marker is what identifies it. Revisit events created before reworks keep their event type and have no rework reason on record.

Did this answer your question?