Merge lp://staging/~akretion-team/project-service/project-service-add-project-typology into lp://staging/~project-core-editors/project-service/trunk

Proposed by Sébastien BEAU - http://www.akretion.com
Status: Work in progress
Proposed branch: lp://staging/~akretion-team/project-service/project-service-add-project-typology
Merge into: lp://staging/~project-core-editors/project-service/trunk
Diff against target: 261 lines (+229/-0)
6 files modified
project_typology/__init__.py (+24/-0)
project_typology/__openerp__.py (+42/-0)
project_typology/i18n/pt_BR.po (+64/-0)
project_typology/project.py (+41/-0)
project_typology/project_view.xml (+55/-0)
project_typology/security/ir.model.access.csv (+3/-0)
To merge this branch: bzr merge lp://staging/~akretion-team/project-service/project-service-add-project-typology
Reviewer Review Type Date Requested Status
Daniel Reis Approve
Raphaël Valyi - http://www.akretion.com Approve
Review via email: mp+211992@code.staging.launchpad.net

Description of the change

Hi,
This module add the concept of typology on task.

To post a comment you must log in.
40. By Sébastien BEAU - http://www.akretion.com

[FIX] commit missing security file

Revision history for this message
Daniel Reis (dreis-pt) wrote :

In my case, "Tags" solved this for me when migratibg from v6 to v7.
Could "Tags" be enough to solve this?

Revision history for this message
Sébastien BEAU - http://www.akretion.com (sebastien.beau) wrote :

Hum I will think about it twice. For now I reject the merge.

Thanks Daniel

Revision history for this message
Daniel Reis (dreis-pt) wrote :

To tell the truth, standard Tags are too flat for me.
So I added a feature to optionally set the allowed Tag/Categs list for each project.
Have a look at it here: https://code.launchpad.net/~dreis-pt/project-service/7.0-project_categ-dr/+merge/195384

Revision history for this message
Sébastien BEAU - http://www.akretion.com (sebastien.beau) wrote :

After thinking twice, I think that the tags can not fit with our need.
Indeed Typology will be used for many thing (like grouping timesheet line on invoicing, default product on task, changing price on sale order masively depending of the typology...) so we really need a many2one as relation and not a many2many.

I put the merge in WIP as we may add some stuff before the merge.

Revision history for this message
Raphaël Valyi - http://www.akretion.com (rvalyi) wrote :

I agree Seb. So basically if category tags are enough for you, don't install this module. But eventually because of their m2m nature, tags don't make the cut and this module is required.

review: Approve
Revision history for this message
Daniel Reis (dreis-pt) :
review: Approve

Unmerged revisions

40. By Sébastien BEAU - http://www.akretion.com

[FIX] commit missing security file

39. By Sébastien BEAU - http://www.akretion.com

[CLEAN] pep 8 clean, remove useless code

38. By Aymeric Lecomte

[IMP] adapt to v7
(../advanced-project-management-70 rev 292)

37. By Raphaël Valyi - http://www.akretion.com

[IMP] project_typology: a ypology can now have a product for easier invoicing/resource allocation
(../advanced-project-management-70 rev 261)

36. By Raphaël Valyi - http://www.akretion.com

[FIX] project_typology: fixed ypo from previous commit
(../advanced-project-management-70 rev 249.1.2)

35. By Raphaël Valyi - http://www.akretion.com

[IMP] project_typology: added dedicated edition menu
(../advanced-project-management-70 rev 249.1.1)

34. By Renato Lima - http://www.akretion.com

translations and fixed current pt_br translations
(../advanced-project-management-70 rev 210)

33. By Vianney - www.akretion.com.br

[FIX] Problem of view, field loaded twice
(../advanced-project-management-70 rev 48.1.5)

32. By Vianney - www.akretion.com.br

[ADD] module to add typologies to organise projects tasks
(../advanced-project-management-70 rev 48.1.3)

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
The diff is not available at this time. You can reload the page or download it.

Subscribers

People subscribed via source and target branches