Skip to content

Conversation

larm-odoo
Copy link
Contributor

Adding new doc for this section that was previously in the Work Entries doc.

Original task card for this PR.

@robodoo
Copy link
Collaborator

robodoo commented Sep 4, 2025

Pull request status dashboard

@larm-odoo larm-odoo self-assigned this Sep 4, 2025
@larm-odoo larm-odoo added the 5 label Sep 4, 2025
@larm-odoo larm-odoo requested a review from jero-odoo September 4, 2025 21:19
@C3POdoo C3POdoo requested a review from a team September 4, 2025 21:20
@larm-odoo
Copy link
Contributor Author

Hi @jero-odoo - this is ready for a peer review. Thanks!

Copy link
Contributor

@jero-odoo jero-odoo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @larm-odoo great work on this! A few notes, also one of the images, time-off-to-report.png, is not compressed.

@larm-odoo larm-odoo force-pushed the 18.0-payroll-add-defer-time-larm branch from 6ef0696 to 3c4b08e Compare September 5, 2025 22:14
@larm-odoo larm-odoo requested a review from Felicious September 5, 2025 22:15
@larm-odoo
Copy link
Contributor Author

Hi @Felicious - this is ready for a final review!

Comment on lines +1 to +3
==================
Time off to report
==================
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi Lara! More lengthy of a comment here (:

Since this is a shorter doc, I'm wondering if you'd like to experiment with our new action-focused document type and rewrite this in a new style. Currently, the doc is clear in explaining the dashboard, context, and examples, but if this document is meant to be read for only one reason (resolve payroll discrepancies), we can shift this doc to be more about what the user needs to do and why.

So instead of titling this "Tiome off to report", for instance, we can title it something like "Resolve time off conflicts".

In addition, I have some questions for you to consider to help reframe this doc in a more action-oriented way:

  • Who is the intended user for this doc (payroll administrators, HR officers, or general employees)?
  • What is the specific goal this user is trying to accomplish when they open this page?
  • At what point in their workflow would the payroll admin land here? Can we structure the doc so they can get from “problem identified” → “steps to fix it” quickly?
  • Can we reframe the introduction: instead of explaining payroll theory, can we start with the problem the user faces (e.g., “An employee’s time off was approved after payroll was processed—what do you do?”)?
  • What is the main decision point for the user—defer multiple entries at once, or handle them one by one?
  • Would it help to start each section title with a verb (e.g., “Defer multiple time off entries” → “Defer multiple entries at once”)?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To give you a sense of the vibe I'm going for, itl'l be something like this:

Defer multiple time off entries

When employees request time off after payroll has already been processed, those entries must be deferred to the next pay period.

  1. Open :menuselection:Payroll app --> Work Entries --> Time Off to Report.
  2. Select the time off requests to defer:
  • To select individual requests, check the box next to each line.
  • To select all requests, check the box at the top of the :guilabel:Employee column.
  1. At the top of the list, click :menuselection:Actions --> Defer to Next Month.
  2. The selected entries are deferred to the following pay period.

Deferring multiple time off entries ensures time off balances remain accurate and eliminates the need to reissue paychecks.

Copy link
Contributor

@Felicious Felicious left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants