-
-
Notifications
You must be signed in to change notification settings - Fork 362
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
[15.0][MIG] analytic_partner: Migration to version 15.0 #573
[15.0][MIG] analytic_partner: Migration to version 15.0 #573
Conversation
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.
Currently translated at 100.0% (5 of 5 strings) Translation: account-analytic-12.0/account-analytic-12.0-analytic_partner Translate-URL: https://translation.odoo-community.org/projects/account-analytic-12-0/account-analytic-12-0-analytic_partner/gl/
Currently translated at 100.0% (5 of 5 strings) Translation: account-analytic-12.0/account-analytic-12.0-analytic_partner Translate-URL: https://translation.odoo-community.org/projects/account-analytic-12-0/account-analytic-12-0-analytic_partner/ca/
Currently translated at 100.0% (5 of 5 strings) Translation: account-analytic-12.0/account-analytic-12.0-analytic_partner Translate-URL: https://translation.odoo-community.org/projects/account-analytic-12-0/account-analytic-12-0-analytic_partner/pt_BR/
Currently translated at 100.0% (5 of 5 strings) Translation: account-analytic-12.0/account-analytic-12.0-analytic_partner Translate-URL: https://translation.odoo-community.org/projects/account-analytic-12-0/account-analytic-12-0-analytic_partner/zh_CN/
Currently translated at 100.0% (5 of 5 strings) Translation: account-analytic-14.0/account-analytic-14.0-analytic_partner Translate-URL: https://translation.odoo-community.org/projects/account-analytic-14-0/account-analytic-14-0-analytic_partner/fr/
Currently translated at 87.5% (7 of 8 strings) Translation: account-analytic-14.0/account-analytic-14.0-analytic_partner Translate-URL: https://translation.odoo-community.org/projects/account-analytic-14-0/account-analytic-14-0-analytic_partner/fr_FR/
ee05e3f
to
4fc7602
Compare
/ocabot migration analytic_partner |
The migration issue (#404) has not been updated to reference the current pull request because a previous pull request (#515) is not closed. |
The text for co-authorship is not correct. It should be |
/ocabot migration analytic_partner |
4fc7602
to
245aee2
Compare
Reviewed. Thanks for the reference. |
Is this ready to merge? @pedrobaeza |
245aee2
to
b0bf2cd
Compare
Search "Show Full Accounting Features". | ||
Make sure your user is included in such group. | ||
Do the same for "Analytic Accounting" group. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are these supposed to numbered bullets?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, I put them that way: #573 (comment)
Why removing them, @stefan-tecnativa ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I hadn't paid attention to it, sorry.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Still incorrect, as there are too much spaces in between.
b0bf2cd
to
864813d
Compare
Co-Authored-By: Stefan Ungureanu <[email protected]>
864813d
to
a964622
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/ocabot merge nobump
On my way to merge this fine PR! |
@pedrobaeza your merge command was aborted due to failed check(s), which you can inspect on this commit of 15.0-ocabot-merge-pr-573-by-pedrobaeza-bump-nobump. After fixing the problem, you can re-issue a merge command. Please refrain from merging manually as it will most probably make the target branch red. |
/ocabot merge nobump |
Hey, thanks for contributing! Proceeding to merge this for you. |
Congratulations, your PR was merged at ed8eb37. Thanks a lot for contributing to OCA. ❤️ |
cc @Tecnativa TT44155
@pedrobaeza please review!
This PR superseeds #515