Currently, our system stores an "action period" in the action_text column to track the duration of a user's task lock for mapping or validating. However, we have identified an issue with the implementation of the task lock extension feature.

The problem lies in the fact that we are not saving the information about how long the task was extended for. As a result, the action_text column remains empty when the task is in the "EXTENDED_FOR_MAPPING" status.

Here's an example of the issue:

As you can see, when the task status changes to "EXTENDED_FOR_MAPPING," there is no duration information provided in the action_text column, unlike when the status is "LOCKED_FOR_MAPPING."

This missing data is crucial for tracking the total duration of task locks accurately, especially when a task is extended multiple times.

Proposed Solution:
To resolve this issue, we need to update our system to include the duration of the task lock extension in the action_text column when the status is "EXTENDED_FOR_MAPPING."

1. When a task lock is extended, calculate the duration of the extension.
2. Ensure that the duration is properly updated each time the task lock is extended.

Steps to Reproduce:

1. Lock a task for mapping/validation.
2. Observe that the action_text column records the lock duration.
3. Extend the task lock before its expiry.
4. Unlock the task.
5. Check the action_text column for the extended task; notice that the duration of the extension is not recorded.