Contributors mailing list archives


Re: New Business Requirement repository [ex-Re: Gap analysis modules]

Elico Corp, Eric Caudal
- 02/06/2016 10:08:42
Hola Nhomar,

<blockquote cite="" type="cite">

On Wed, Jun 1, 2016 at 7:37 PM, Eric Caudal <> wrote:

Later ideally we should freeze the current version in v8 and start migration to v9. For this part we need help, mostly on reviewing, testing, debugging, etc (usual community work).
Another topic for help is currently we use an experimental docx reporting engine for BR report. It works but has limitations (mostly in handling html code) and it is not that beautiful. We need to plan a clean qweb version.

then I think we can use a similar approach for docx (but BT, I prefer stay into good PDF reporting with some kind of rst/md support) than use MS office jeje. (we can discuss afterwards that).
[EC] Your tool seems cool but I am not sure we are talking about the same thing.
Current reports are based on docx template that we render (via jinja2) into pdf (this is an experimental tool of ours:
We should simply come back to pure qweb.
<blockquote cite="" type="cite">

This is only part of the roadmap which includes for longer term:
* change request management

I supose the flow right?
[EC] not sure about your question here.
I am talking about the possibility to amend an original requirement with workflow + estimation modification and approval + and complementary project/tasks creation
Currently we just have a simple checkbox for filter management
<blockquote cite="" type="cite">

* integration with earned value reporting

I need more context, what are you planning here?
[EC] please check and
<blockquote cite="" type="cite">

* BI report (we have one but needs cleansing)

I can help once I start use it when my DB is migrated to v9.0 (Now I am full and We have pretty stable v8.0 but for sure I am planning migrate manually our User History tool to a better approach, the it will be a mix of New Odoo's + Ours + Yours for sure).
[EC] This is not first priority as we need to stabilize the models first so we can take that up once we are all familiar with the concepts
<blockquote cite="" type="cite">

* Complex parenting (parent/child/depends on/mandatory/options/etc)

I need check it... No too much info here
[EC] refer to
but not only. Check Jordi's comment here which explain better than me:
<blockquote cite="" type="cite">

* integration with etherpad (which provide some version control)

Did you check the document page approach under OCA? I think we need extend that in order to have a manual management mixed with ISO's ones, I think that should be the proper approach.
[EC] good suggestion. All in all is to be able to version control the documents we send to the customer
<blockquote cite="" type="cite">

Nhomar Hernandez
CEO Vauxoo.
Twitter: @nhomar
Odoo Gold Partner
Skype: nhomar00 (Envia mail previo no lo superviso siempre).
Móvil Venezuela:
+58 4144110269
Móvil México:
+52 1 4773933942

Post to: