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

[17.0][FIX] project_task_add_very_high: move priority field outside title in sharing project task view form #1385

Open
wants to merge 1 commit into
base: 17.0
Choose a base branch
from

Conversation

sanderlienaerts
Copy link

Before this commit, the priority field was misplaced in the project's sharing project task view form (portal users editable task view).
Screenshot 2024-11-29 at 11 17 00

After this commit, the exact solution as used in the webclient's project task view form is used for the editable portal view. This solves the misplacement of the field.
Screenshot 2024-11-29 at 11 11 36

@OCA-git-bot
Copy link
Contributor

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

@sanderlienaerts sanderlienaerts force-pushed the 17.0-project_task_add_very_high-fix-portal-editable-view branch from 4e98929 to b9122c5 Compare November 29, 2024 10:20
Copy link

@coleste coleste left a comment

Choose a reason for hiding this comment

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

LGTM

@OCA-git-bot
Copy link
Contributor

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). 🤖

@pedrobaeza pedrobaeza changed the title [FIX] project_task_add_very_high: move priority field outside title in sharing project task view form [17.0][FIX] project_task_add_very_high: move priority field outside title in sharing project task view form Dec 17, 2024
@pedrobaeza pedrobaeza added this to the 17.0 milestone Dec 17, 2024
Copy link
Member

@pedrobaeza pedrobaeza left a comment

Choose a reason for hiding this comment

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

In Odoo core, the priority field is placed in the same line as the title:

imagen

With your change, you are wasting a whole line just for the stars. The change should be instead to extend the space for the 3 stars.

Please also don't change the manifest version, as that's done by the bot on merging (and undo also the index.html change).

@sanderlienaerts
Copy link
Author

Hi @pedrobaeza, this PR recreates the same behavior in the portal view as the form in the webclient for logged in project users. Which, if I am not mistaken, is currently also not following Odoo's core in-line behavior.

Do you suggest both forms should follow the Odoo core's behavior?

@pedrobaeza
Copy link
Member

Well, at least the backend form view. Adding 2 stars shouldn't take one vertical line more, making the ergonomics worst.

@sanderlienaerts
Copy link
Author

sanderlienaerts commented Dec 19, 2024

All right. I agree with you that it should be in-line.

However testing this bug in v18, it seems the misalignment is no longer present there and debugging why this is happening in v17, is going to be a lot of work (probably an odoo client thing).

Therefore my suggestion would be to implement this fix for v17, so that the portal and back-end views replicate the same implementation and behaviours. Then for the migration to v18, both views adjustments should be removed, so that the priority field is in-line for the back-end and portal view.

v18:
Screenshot 2024-12-19 at 12 30 17

Removing the view adjustments (x2) for v18:

<xpath expr="//div[hasclass('oe_title')]" position="before">
   <field name="priority" position="move" />
</xpath>

To make sure we're on the same page, this is the current v17 behaviour

Back-end form

Screenshot 2024-12-19 at 12 38 46

Portal share view

Screenshot 2024-12-19 at 12 39 22

@sanderlienaerts sanderlienaerts force-pushed the 17.0-project_task_add_very_high-fix-portal-editable-view branch from b9122c5 to d40d55d Compare December 19, 2024 11:37
@pedrobaeza
Copy link
Member

I don't see this patch brings any enhancement. At the end, we have the same 2 lines before and after. I think a simple CSS override may fix it.

@pedrobaeza
Copy link
Member

@pilarvargas-tecnativa can you try a bit to fix the situation?

@pilarvargas-tecnativa
Copy link
Contributor

@pilarvargas-tecnativa can you try a bit to fix the situation?

Ok I'll take a look

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

Successfully merging this pull request may close these issues.

6 participants