Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[16.0][FIX] hr_timesheet_name_customer: better impl with compute #744

Merged
merged 1 commit into from
Feb 28, 2025

Conversation

sbidoul
Copy link
Member

@sbidoul sbidoul commented Feb 28, 2025

Before this commit, the creation would fail when no 'name' value was provided.

Before this commit, the creation would fail when no 'name' value was provided.
@OCA-git-bot
Copy link
Contributor

Hi @solo4games, @CetmixGitDrone,
some modules you are maintaining are being modified, check this out!

@sbidoul sbidoul changed the title [FIX] hr_timesheet_name_customer: better impl with compute [16.0][FIX] hr_timesheet_name_customer: better impl with compute Feb 28, 2025
Copy link
Member

@ivs-cetmix ivs-cetmix left a comment

Choose a reason for hiding this comment

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

Looks, reasonable!
LGTM

Copy link

@Aldeigja Aldeigja left a comment

Choose a reason for hiding this comment

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

LGTM

Copy link
Contributor

@CRogos CRogos left a comment

Choose a reason for hiding this comment

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

The change LGTM.

The module itself is a little strange. I see the intention, but e.g. when the name is updated, the name_customer isn't. (even though it wasn't different before, and the normal user doesn't see it)
Also when reading name customer I was thinking to replicate the customer name (partner_id.name). Wouldn't be name_report_overwrite a better choise and leave it empty if it is the same as the name attribute... only some ideas

@sbidoul
Copy link
Member Author

sbidoul commented Feb 28, 2025

I agree. I don't use this module I'm just here to get the branch green.

/ocabot merge patch

@OCA-git-bot
Copy link
Contributor

Hey, thanks for contributing! Proceeding to merge this for you.
Prepared branch 16.0-ocabot-merge-pr-744-by-sbidoul-bump-patch, awaiting test results.

@OCA-git-bot
Copy link
Contributor

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

@OCA-git-bot OCA-git-bot merged commit 04e9657 into OCA:16.0 Feb 28, 2025
8 of 9 checks passed
@sbidoul sbidoul deleted the 16.0-fix-hr-timesheet-name-customer branch February 28, 2025 15:30
@ivs-cetmix
Copy link
Member

The change LGTM.

The module itself is a little strange. I see the intention, but e.g. when the name is updated, the name_customer isn't. (even though it wasn't different before, and the normal user doesn't see it) Also when reading name customer I was thinking to replicate the customer name (partner_id.name). Wouldn't be name_report_overwrite a better choise and leave it empty if it is the same as the name attribute... only some ideas

@CRogos thank you for your feedback. Yup, it might look strange, but it does a good job allowing to have separate description in timesheet reports for clients. It's extremely important eg case your devs log some technical details while client wants to see more business context in report. For the very same reason customer description doesn't change when the description itself is updated.
Regarding the module name, this is solely technical. "Description" field has a technical name "name", so "Description Customer" is "name_customer".

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

Successfully merging this pull request may close these issues.

5 participants