[16.0] [ADD] website_slides_attendees_completed_time: show completed time in attendee views

[rrebollo]

This module extends the functionality of course attendee views to show course's completed time.

After module installation, you will see course's completed time within attendee views.

@BinhexTeam

[rrebollo]

[christian-ramos-tecnativa]

Let me know if I explained myself properly. Thanks

[christian-ramos-tecnativa]

Functional and code review, LGTM

[rrebollo]

✅ Update on the Approach Taken

Hello @Christian-RB and community,

After careful consideration, we’ve decided to align with the native _recompute_completion approach for tracking course progress. This decision has greatly simplified the logic and integration, and the overall flow of the feature now feels much smoother.

🔄 What Changed

The key update alongside this decision is that the field completed_time is no longer a computed field. Instead, it’s now a stored field that must be initialized with data when the addon is installed.

To ensure this, we’ve implemented a post_init_hook, which populates the completed_time values for all existing attendee records based on their current completed slides.

🧪 Tests Included

We’ve also added a suite of unit tests. These were designed following the pattern of the native tests for the completion field (which corresponds to the Progress column in the attendee view).

It’s important to highlight that although the completed_time and completion fields share similar purposes, their logic is not interchangeable:

• completion (Progress) is slide-count based
• completed_time is time-duration based and must remain an accurate, real-time reflection of the attendee’s completed course content

This means that updates to completed_time must respond to changes like:

• Slides being archived or restored
• Slides being marked as incomplete
• Course structure being modified

We believe this dual-tracking (count-based + time-based) gives a more robust and insightful representation of learner engagement.

---

We’re now just awaiting the community’s feedback. Thanks for reviewing!

[christian-ramos-tecnativa]

@rrebollo Can you add the version [16.0] in the PR title? Thanks

[edescalona]

LGTM

[OCA-git-bot]

This PR has the approved label and has been created more than 5 days ago. It should therefore be ready to merge by a maintainer (or a PSC member if the concerned addon has no declared maintainer). 🤖

[github-actions]

There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this PR to never become stale, please ask a PSC member to apply the "no stale" label.

[rrebollo]

• @jelenapoblet maybe we could reopen this in order to get it merged?

[jelenapoblet]

Hi @rrebollo is this necessary when a progress field already exists?

[rrebollo]

@jelenapoblet we anticipate this concern. From a comment above 👉:

It’s important to highlight that although the completed_time and completion fields share similar purposes, their logic is not interchangeable:

• completion (Progress) is slide-count based
• completed_time is time-duration based and must remain an accurate, real-time reflection of the attendee’s completed course content

And from the addon's documentation:

Built-in (Odoo):

• Progress = Number of Completed Slides / Total Number of Slides →
  A simple ratio, based only on slide count.
  Added by this addon:
• Completed Time = Σ(completion_time of each completed slide) → A
  cumulative total of time-based effort for each attendee.

🧪 Example
^^^^^^^^^^
For a course with 10 slides (total 20 hours), if an attendee completes:

• 1 slide of 15 hours → Progress: 10% → Completed Time: 15h

[rrebollo]

ping @jelenapoblet comment

[jelenapoblet]

@rrebollo are you also going to maintain this ? is there a plan to migrate this module to v17, 18 and 19 ?

[rrebollo]

@rrebollo are you also going to maintain this ? is there a plan to migrate this module to v17, 18 and 19 ?

Yes and yes

[jelenapoblet]

/ocabot merge nobump

[OCA-git-bot]

Sorry @jelenapoblet you are not allowed to merge.

To do so you must either have push permissions on the repository, or be a declared maintainer of all modified addons.

If you wish to adopt an addon and become it's maintainer, open a pull request to add your GitHub login to the maintainers key of its manifest.

[pedrobaeza]

/ocabot merge nobump

[OCA-git-bot]

On my way to merge this fine PR!
Prepared branch 16.0-ocabot-merge-pr-10-by-pedrobaeza-bump-nobump, awaiting test results.

[OCA-git-bot]

Congratulations, your PR was merged at 5bb17db. Thanks a lot for contributing to OCA. ❤️