Skip to content

[19.0][IMP] contract: show the contract name in bold in the list view - #1519

Closed
bosd wants to merge 1 commit into
OCA:19.0from
bosd:19.0-imp-contract-bold-name-column
Closed

[19.0][IMP] contract: show the contract name in bold in the list view#1519
bosd wants to merge 1 commit into
OCA:19.0from
bosd:19.0-imp-contract-bold-name-column

Conversation

@bosd

@bosd bosd commented Sep 5, 2026

Copy link
Copy Markdown
Contributor

Spotted on the 19.0 runboat: contracts look flat next to the sale orders and bills they sit beside in the same menus.

Problem

Odoo puts the identifying column of a document list in bold, so a row can be scanned by its name before anything else.

sale.order:

<field name="name" string="Number" readonly="1" decoration-bf="1"/>

account.move:

<field name="name" decoration-bf="1" .../>

It is a broad convention - decoration-bf appears 61 times across core views. contract_contract_tree_view is the odd one out:

<field name="name" string="Name" />

no decoration-bf, so the contract name renders in normal weight.

Change

Add decoration-bf="1" to that one field.

Not touched

The contract template and contract tag lists also have a plain name column, but those are configuration models rather than documents sitting next to invoices, so they are left alone. The contract line list is left alone too: there name is the line description, and core does not bold the description column of a document's lines either.

Independent of #1517, which touches other columns of the same list.

Odoo puts the identifying column of a document list in bold, so a row can
be scanned by its name before anything else. `sale.order` does it:

    <field name="name" string="Number" readonly="1" decoration-bf="1"/>

and so does `account.move`:

    <field name="name" decoration-bf="1" .../>

The contract list is the odd one out. Its name column carries no
`decoration-bf`, so contracts render flat next to the sale orders and bills
they sit beside in the same menus.

Add `decoration-bf="1"` to match.
@bosd

bosd commented Sep 5, 2026

Copy link
Copy Markdown
Contributor Author

Folding this into #1427 instead. The revamp commit there already promotes the same field from <h3> to <h1> in the form view, so the list and the form now get the contract name treated consistently in one place rather than two PRs pulling at the same field.

Superseded by #1427; no separate branch needed.

@bosd bosd closed this Sep 5, 2026
bosd pushed a commit to bosd/contract that referenced this pull request Sep 5, 2026
Add decoration-bf="1" to the name field in contract_contract_tree_view so the
contract name renders bold, matching sale.order / account.move. Bump
19.0.1.1.7 -> 19.0.1.1.8.
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.

2 participants