Skip to content

Conversation

@AmalBenAissa
Copy link

Migration module analytic_partner to version 18.0

@AmalBenAissa AmalBenAissa mentioned this pull request Aug 26, 2025
16 tasks
@DorianMAG
Copy link

Hi @AmalBenAissa
Can you squash your commits plz?

Copy link
Member

@flotho flotho left a comment

Choose a reason for hiding this comment

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

I've installed the module here http://oca-account-analytic-18-0-pr823-611933295916.runboat.odoo-community.org/odoo/action-286 but I'm not able to reach the analytic lines.
could you elaborate the README and the process.
Otherwise, the code LGTM

Usage
=====

1. Go to **Invoicing > Accounting > Management > Analytic Items**.
Copy link
Member

Choose a reason for hiding this comment

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

Same comment here

Choose a reason for hiding this comment

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

You're right, Management section doesn't exist.

Copy link
Author

Choose a reason for hiding this comment

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

updated this instruction in readme file

type="action"
name="%(act_analytic_cost_revenue)d"
icon="fa-usd"
string="Cost/Revenue"
Copy link
Member

Choose a reason for hiding this comment

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

Could you add default values in the context so that create will be eased during the creation

@AmalBenAissa AmalBenAissa force-pushed the 18.0-mig-analytic_partner branch from 6119332 to ff26ba1 Compare August 28, 2025 09:35
@AmalBenAissa
Copy link
Author

Hi @AmalBenAissa Can you squash your commits plz?

hello @DorianMAG thanks for the request that is done

Copy link

@luisDIXMIT luisDIXMIT left a comment

Choose a reason for hiding this comment

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

Tested on runboat and LGTM, just change the PR title to "[18.0] [MIG] analytic_partner: Migration to 18.0". It's a convenion to easily search it and identify.

@AmalBenAissa AmalBenAissa changed the title 18.0 mig analytic partner [18.0] [MIG] analytic_partner: Migration to 18.0 Aug 29, 2025
[MIG] analytic_partner : Migration to 18.0

[MIG] analytic_partner : Migration to 18.0

update readme file
@AmalBenAissa AmalBenAissa force-pushed the 18.0-mig-analytic_partner branch from d2168b2 to 9676278 Compare August 29, 2025 10:37
Copy link
Member

@flotho flotho left a comment

Choose a reason for hiding this comment

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

Tested on runboat.
Doc is Ok, y bad
LGTM

@flotho
Copy link
Member

flotho commented Aug 29, 2025

ping @OCA/accounting-maintainers any chance to have a merge here ?

Copy link

@DorianMAG DorianMAG left a comment

Choose a reason for hiding this comment

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

Functional test.
LGTM
Thx for this work

Copy link
Member

@Saran440 Saran440 left a comment

Choose a reason for hiding this comment

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

@flotho
Copy link
Member

flotho commented Nov 7, 2025

ping @AmalBenAissa , some changes are requested, could you fix SVP ?

pedrobaeza and others added 12 commits December 10, 2025 12:34
Classify analytic items by partner
==================================

This module adds a partner on each analytic item for allowing to have another
dimension for analysing data.

It also handles the proper propagation of this field to the created analytic
entries when validating invoices.

Configuration
=============

You have to be granted as at least "Accountant" in your user profile and
have checked the "Analytic Accounting" access right.

Usage
=====

Go to Accounting > Analytic Journal Items, and there, you can set the partner
for the analytic items, and search or group by it.

You can also go to a partner, and click on the smart-button "Cost/Revenue",
placed on the upper-right part, and you will navigate to the analytic items
associated to this partner.

Known issues / Roadmap
======================

* This module hasn't been tested with *account_analytic_plans* module
installed, so maybe it's incompatible with it.
* IMP: Distinguish between the partner of the account and the specific partner
* FIX: Allow grouping on partner_id field. Fixes OCA#41
* FIX: README - Indentation is not correct in Known issues.
@AmalBenAissa
Copy link
Author

@Saran440 done , could you check please ?

@Saran440
Copy link
Member

@AmalBenAissa Thanks for the fix. Please read the instructions here: https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-18.0#how-to
and then open a new PR or force push to this PR.

@DorianMAG
Copy link

Hi @Saran440,

Could you clarify the problem?
Is it necessary to squash the last commit?

It seems the history was preserved correctly.

Best regards

@Saran440
Copy link
Member

@DorianMAG

Could you clarify the problem?

  • Reviewer can't review the code difference between the original history and the new commit.

Is it necessary to squash the last commit?

  • The history commit should come first, and then the migration commit, so reviewers can clearly check the code changes.

However, if the maintainer is fine with this PR, I’m fine with it too.

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.