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

[MIG] crm_claim: Migration to 14.0 #370

Closed
wants to merge 20 commits into from

Conversation

redapureskill
Copy link
Contributor

Migrating crm_claim from V13 to V14:

#TODO Change version in manifest.py file : Done.
#TODO Migration process file crm_claim.data : {
crm_claim_data.xml : Done.
} : Done.
#TODO Migration process file crm_claim.demo : {
crm_claim_demo.xml : Done.
} : Done.
#TODO Migration process file crm_claim.models : {
crm_claim.py : Done.
crm_claim_category.py : Done.
crm_claim_stage.py : Done.
res_partner.py : Done.

} : Done
#TODO Migration process file crm_claim.report : {
crm_claim_report.py : Done.
crm_claim_report_view.xml : Done.
}: Done.
#TODO Migration process file crm_claim.tests : Done.
#TODO Migration process file crm_claim.report :{
crm_claim_view.xml : Done.
crm_claim_category_view.xml : Done.
crm_claim_stage_view.xml : Done.
res_partner_view.xml : Done.
}: Done.

cubells and others added 19 commits November 15, 2020 15:47
Include record rule for multi-company.
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate.

Translation: crm-13.0/crm-13.0-crm_claim
Translate-URL: https://translation.odoo-community.org/projects/crm-13-0/crm-13-0-crm_claim/
The Claim form's statusbar is intended to be clickable, but Odoo 13 is
apparently no longer compatible with `clickable="True"`. Instead, either
`clickable="1"` or `options="{'clickable': 1}"` must be used. Odoo core
code uses the latter, so the Claim form has been updated to match core
convention.
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate.

Translation: crm-13.0/crm-13.0-crm_claim
Translate-URL: https://translation.odoo-community.org/projects/crm-13-0/crm-13-0-crm_claim/
This was referenced Nov 15, 2020
Copy link
Contributor

@skeller1 skeller1 left a comment

Choose a reason for hiding this comment

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

👍 LGTM code and functional review locally (runbot is not working at the moment)

Maybe one wish: adding ondelete="restrict" to stage_id and categ_id fields in crm.claim model to prevent information loss. but this is not blocking.

Thank you for supporting OCA

"name": "Claims Management",
"version": "14.0.1.0.0",
"category": "Customer Relationship Management",
"author": "Odoo S.A., " "Tecnativa, " "Odoo Community Association (OCA)",
Copy link
Contributor

Choose a reason for hiding this comment

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

Odoo S.A., " "Tecnativa, " "Odoo Community Association (OCA) => Odoo S.A., Tecnativa, Odoo Community


To configure this module, you need to:

* Go to new menu **CRM > Configuration > Claim > Categories** and create as
Copy link
Contributor

Choose a reason for hiding this comment

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

maybe we could add the information that we have to do this in debug mode

</p>
<p>
Create claim categories to better manage and classify your
claims. Some example of claims can be: preventive action,
Copy link
Contributor

Choose a reason for hiding this comment

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

Maybe i am wrong: examples instead of example

@Reyes4711-S73
Copy link
Contributor

Functional review

<field name="date_deadline" attrs="{'invisible': [(1, '=', 1)]}" />
<field name="date_closed" attrs="{'invisible': [(1, '=', 1)]}" />
<field name="company_id" groups="base.group_multi_company" />
<field attrs="{'invisible': [(1, '=', 1)]}" name="date_deadline" />

Choose a reason for hiding this comment

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

Why we need to change this?

Copy link
Contributor

Choose a reason for hiding this comment

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

And I don't think it works properly. It shows only header, without data, it does not make any sense.

/>
</header>
<sheet string="Claims">
<group>
<field name="name" />
<field name="date" />
<field name="company_id" groups="base.group_multi_company" />
<field groups="base.group_multi_company" name="company_id" />

Choose a reason for hiding this comment

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

Is it mentioned somewhere to use groups first and then name?

@@ -7,7 +7,7 @@
"name": "Claims Management",
"version": "14.0.1.0.0",
"category": "Customer Relationship Management",
"author": "Odoo S.A., Tecnativa, Odoo Community",
"author": "Odoo Community Association (OCA)",

Choose a reason for hiding this comment

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

Why authors are removed?

Copy link

Choose a reason for hiding this comment

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

@redapureskill Please restore Odoo SA and Tecnativa as authors. Then I could merge this.

Choose a reason for hiding this comment

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

@NL66278 This changes among others are done in this #391

Copy link

Choose a reason for hiding this comment

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

@Daniel-CA I do not quite understand what you mean with the reference to the other PR. We should not just delete authors...

Copy link
Member

Choose a reason for hiding this comment

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

Please review the other PR as superseding this one.

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

Copy link

@claudiagn claudiagn left a comment

Choose a reason for hiding this comment

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

functional review ok! LGTM

Copy link
Contributor

@simahawk simahawk left a comment

Choose a reason for hiding this comment

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

as per #368 fix the build first 🙏

@anajuaristi
Copy link

Hello
@simahawk #368 is related to crm_lead and this is crm_claim, so they are different objects. Am I missing something?

On the other side, I tested functionally crm_claim on V14 and LGTM 👍

@simahawk
Copy link
Contributor

simahawk commented Apr 12, 2021

Hello
@simahawk #368 is related to crm_lead and this is crm_claim, so they are different objects. Am I missing something?

On the other side, I tested functionally crm_claim on V14 and LGTM +1

Ciao Ana! :)

I know but the point is that nobody will be able to merge PR till that issue is gone.

@simahawk simahawk changed the title 14.0 mig crm claim [MIG] crm_claim: Migration to 14.0 Apr 12, 2021
@oihane
Copy link
Contributor

oihane commented Apr 13, 2021

Hello
@simahawk #368 is related to crm_lead and this is crm_claim, so they are different objects. Am I missing something?
On the other side, I tested functionally crm_claim on V14 and LGTM +1

Ciao Ana! :)

I know but the point is that nobody will be able to merge PR till that issue is gone.

fix done in #388

@redapureskill
Copy link
Contributor Author

Hello
@simahawk #368 is related to crm_lead and this is crm_claim, so they are different objects. Am I missing something?
On the other side, I tested functionally crm_claim on V14 and LGTM +1

Ciao Ana! :)
I know but the point is that nobody will be able to merge PR till that issue is gone.

fix done in #388

still some checks not successfull please check #388

@Daniel-CA
Copy link

@redapureskill You should check too @dsolanki-initos stated

@oihane
Copy link
Contributor

oihane commented Apr 14, 2021

@redapureskill you should rebase, even there was a check in red, was a minor problem because there was no report to compare with.

@anajuaristi
Copy link

Hello, is important you make rebase to Travis be able to pass.
It would be great if we could merge this ASAP

@dsolanki-initos
Copy link

It would be great if this PR is merged.

@simahawk
Copy link
Contributor

@dsolanki-initos @redapureskill someone has to rebase it 😉

@dsolanki-initos
Copy link

Hi @redapureskill it would be great if you could rebase it so that this PR can be merged .

@dsolanki-initos
Copy link

Hi @redapureskill is it possible to rebase? we need to merge it ASAP.

@dsolanki-initos
Copy link

Hi @redapureskill can you please rebase as we need to merge it ASAP.

@anajuaristi
Copy link

@dsolanki-initos @simahawk @oihane @Daniel-CA

Hi tech people. I think @redapureskill is not reading the messages or he is too busy to go on with this. I propose to make a manual merge ourselves.
Please comment if it's possible and if you consider it would be right if we do it.
Thank you!
Ana

@Daniel-CA
Copy link

I have done another PR with last fixes and updated. #391

@redapureskill
Copy link
Contributor Author

Hi @redapureskill can you please rebase as we need to merge it ASAP.

fixed and rebased, sorry mom passed away!

@redapureskill
Copy link
Contributor Author

LGTM

@redapureskill redapureskill requested a review from simahawk June 2, 2021 09:11
@dsolanki-initos
Copy link

Seems that PR is Ready to merge It would be great if it could merged

@pedrobaeza
Copy link
Member

Superseded by #391

@pedrobaeza pedrobaeza closed this Jun 7, 2021
@redapureskill redapureskill deleted the 14.0-mig-crm_claim branch June 7, 2021 07:45
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.