Description
Users with Super Admin/OKR admin/OKR manager roles can view and edit check-in values for key results of a specific team objective.
Acceptance Criteria
-
Super Admins & OKR admins can view and edit check-in history for all of the existing team objectives' key results within the organization.
-
OKR managers, however, can only view and edit check-in history for Team Objectives' key results that they have created.
-
OKR managers cannot view or edit check-in history for Team Objectives' key results that have been created by Super Admins & OKR admins.
-
Users with the 'Employee' role can not view the check-in history of the key results.
-
In the table within the Team Objectives page, the rows that represent the objective records will be clickable. The user can click on the record to view that specific team objective.

- Click on the 'Key Results' tab to access the key results that have been created for the Team Objective.

- The user can click the kebab menu on the key result component to access the 'View Checking History' option.


- Once the user clicks the 'View Checking History' option, the user will be navigated to the 'Check In History' page.

-
All of the check-ins that have been added will be listed as above.
-
If a user hovers on top of the check-in record, the edit icon will be displayed on the right side of the component.

- To edit a specific check-in record, click on the edit icon, which will prompt the 'Edit Check In' modal.

-
The user will not be able to edit the 'Date' field which will be disabled by default when editing the Check-In record.
-
The user can edit the value accordingly.
-
The 'Save changes' button will be disabled until there are changes; it will be enabled once a change has been made to the existing content.
-
The user can click on the cancel button to discard the changes.
-
The user can save all the changes by clicking on the 'Save changes' button.
-
Once the changes are saved successfully, display the following success toast message;
Title: Check-in record updated
Message: Check-in record was updated successfully!
-
Once the changes have been saved, the changes must be plotted accordingly in the key result graph and update the 'Current Value' if needed. (Current value will be updated accordingly if the user edits the most recent check-in record)
-
If the changes weren't saved successfully, for a general reason (API failure), display the following error toast message;
Title: Oops! Something went wrong.
Message: Failed to update the check-in, please try again.
Description
Users with Super Admin/OKR admin/OKR manager roles can view and edit check-in values for key results of a specific team objective.
Acceptance Criteria
Super Admins & OKR admins can view and edit check-in history for all of the existing team objectives' key results within the organization.
OKR managers, however, can only view and edit check-in history for Team Objectives' key results that they have created.
OKR managers cannot view or edit check-in history for Team Objectives' key results that have been created by Super Admins & OKR admins.
Users with the 'Employee' role can not view the check-in history of the key results.
In the table within the Team Objectives page, the rows that represent the objective records will be clickable. The user can click on the record to view that specific team objective.
All of the check-ins that have been added will be listed as above.
If a user hovers on top of the check-in record, the edit icon will be displayed on the right side of the component.
The user will not be able to edit the 'Date' field which will be disabled by default when editing the Check-In record.
The user can edit the value accordingly.
The 'Save changes' button will be disabled until there are changes; it will be enabled once a change has been made to the existing content.
The user can click on the cancel button to discard the changes.
The user can save all the changes by clicking on the 'Save changes' button.
Once the changes are saved successfully, display the following success toast message;
Once the changes have been saved, the changes must be plotted accordingly in the key result graph and update the 'Current Value' if needed. (Current value will be updated accordingly if the user edits the most recent check-in record)
If the changes weren't saved successfully, for a general reason (API failure), display the following error toast message;