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 10.0 #170

Merged
merged 4 commits into from
Sep 30, 2017
Merged

Conversation

cubells
Copy link
Sponsor Member

@cubells cubells commented Sep 5, 2017

As crm_claim is not available in odoo v10.0, we migrate crm_claim to oca.

cc @Tecnativa

@yajo yajo added this to the 10.0 milestone Sep 5, 2017
@cubells cubells force-pushed the 10.0-mig-crm_claim branch 2 times, most recently from d179033 to 110c33d Compare September 5, 2017 14:52
@cubells cubells mentioned this pull request Sep 5, 2017
1 task
@cubells cubells force-pushed the 10.0-mig-crm_claim branch 2 times, most recently from 2dc1eb9 to 290ef5e Compare September 5, 2017 16:28
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.

Good work. Please check if we can get full test coverage.


from odoo import fields, models, tools

AVAILABLE_PRIORITIES = [
Copy link
Member

Choose a reason for hiding this comment

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

Put directly this on the field. I haven't seen this used in any other place. Am I right?


tools.drop_view_if_exists(self._cr, 'crm_claim_report')
self._cr.execute("""
create or replace view crm_claim_report as (
Copy link
Member

Choose a reason for hiding this comment

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

Please split this query to be inheritable.

@pedrobaeza
Copy link
Member

@rafaelbn @luismontalba please review

* Go to new menu **CRM > Configuration > Claim > Categories** and create as
many categories as you need.
* Go to new menú **CRM > After Sale > Services > Stages** and create stages for
claims.
Copy link
Member

@luismontalba luismontalba Sep 8, 2017

Choose a reason for hiding this comment

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

Sales > Configuration > Claim > Stages

Copy link
Sponsor Member Author

Choose a reason for hiding this comment

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

This menu exists if you have installed sales module. If not, correct menu is CRM > Configuration > Claim > Stages

This module only depends on sales_team.

Copy link
Member

@luismontalba luismontalba 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 runbot (minor changes proposed)

Copy link
Member

@chienandalu chienandalu left a comment

Choose a reason for hiding this comment

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

Just some quick comments

<field name="model">crm.claim.stage</field>
<field name="arch" type="xml">
<tree string="Claim Stages">
<field name="sequence"/>
Copy link
Member

Choose a reason for hiding this comment

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

A widget="handle" would fit here, don't you think?

<form string="Claim Stage">
<group col="4">
<field name="name"/>
<field name="case_default"/>
Copy link
Member

Choose a reason for hiding this comment

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

Isn't it a little bit hard to know wich team a stage belongs to?

Copy link
Sponsor Member Author

Choose a reason for hiding this comment

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

You can't know which team a stage belongs to, because stage isn't a field of crm.team model.

Case_default is used to assign a default stage based on team to crm_claim

Copy link
Member

Choose a reason for hiding this comment

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

@cubells please answer this

Copy link
Member

@bodedra bodedra Oct 1, 2017

Choose a reason for hiding this comment

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

@chienandalu I am agree with your point. We have to set case_default to True. To overcome these situation, we can visible Teams field into Stage. Afterwards above domain will works fine. I have created PR (#178) for that.

@max3903 max3903 merged commit 0e8091b into OCA:10.0 Sep 30, 2017
@pedrobaeza
Copy link
Member

@max3903 there's still a comment unattended. Why do you merge?

@pedrobaeza pedrobaeza deleted the 10.0-mig-crm_claim branch September 30, 2017 14:46
@max3903
Copy link
Sponsor Member

max3903 commented Sep 30, 2017

@pedrobaeza Sorry, I didn't see the pending comment. I saw the 2 approved reviews and the "needs review" tag.

@pedrobaeza
Copy link
Member

OK, let's see if there's something to change and if so, we propose a new PR.

@bodedra
Copy link
Member

bodedra commented Oct 1, 2017

#178

@gurneyalex gurneyalex mentioned this pull request Sep 25, 2018
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.

None yet

7 participants