The addon analytic_hours_block is well installing. But you are not able to use it with standard account_invoice.
In fact, the addon is refering an invoice.department_id, wich does not exist:

'department_id': fields.related(
            'invoice_id', 'department_id',
             type='many2one',
             relation='hr.department',
             string='Department',
            store={
                'account.hours.block': (lambda self, cr, uid, ids, c=None: ids,
                                        ['invoice_id'], 10),
                'account.invoice': (_get_invoice, ['department_id'], 10),
            },
             readonly=True),

Saving a newly created hours block results in this error:
KeyError: "Field 'department_id' does not exist in object 'browse_record(account.invoice, ...)'"

I had to modify the manifest - my database isn't configured for demo data (so I don't want demo data unless it is) and I have deleted the Odoo Sample Project.

Don't need any action, just reporting.

Probably related to #97

We have Contracts (Analytic Account) that include Corrective and Preventive maintenance services.

I would like to be able to define generic Maintenance Plans, and on each Contract define what Maintenance Plan (many2one) to be used.
At this point the Maintenance Plan structure required is quite simple: just set a period between services. For example: every 6 months, or every 12 months.

Basic Maintenance Plans:

• Add the "Maintenance Plan" model, defining a period between services: period type is "months" or "days"; period number is a float.
• Add to Contracts a "Maintenance Plan" many2one field.
• Add to Contracts a "Next Service Date" allowing manual input.
• Add to Contracts a "Last Service Date" for manual input, with an onchange to automatically compute the "Next Service Date" based on the Maintenance Plan period.

As an option, we could use Tasks to manage Preventive service:

• Add a "Template Service Task" many2one field to Maintenance Plans.
• Add a "Next Service Task" many2one to Contracts.
• When a Maintenance Plan is set on a Contract, the "Next Service Task" is generated from the template.
• The Contract "Next Service Date" is the Next Service Task Deadline Date (a non editable related field).
• Add a "Last Service Task" field to Contracts.
• When the "Next Service Task" is done, it is set as the "Last Service task", and a new "Next Service Task" is automatically generated.
• The Contract "Last Service Date" is the "Last Service Task" Deadline Date (a non editable related field).

Hello,

I'm a bigginer in odoo. I face an issue while trying to and I want to fixe it. there is no control made on start_date and end_date while creating a project under odoo 8

Please help

i have install Project Task Default Stage on v10 but it has error The error is Error: Unknown field state in domain [["state","in",["cancelled","close"]]] when i try to click to seting plz help

just testing the bug process in this project!

Hi, for some reason can't fin the way to setup the "control date" field.

The error is:

"The following fields are invalid: Model"

I'm working with odoo 8.x.

Can you help me out with this?

Module adds / sign to issue's header and uneditable ID field. In odoo 8 works nice

For project managers that need to categorize different project for different purposes found that is installed both modules:
project_categ and project_categ_issue both offer a way to categorize Projects.

Then, how to decide which one is more important in order to categorize?
Furthermore the string that user could read means that is the root category for Task and the other is for Issues. So is not the main purpose to categorize projects and none of them are mandatory on Project form.

My point is we should introduce a new model:
class_name ProjectCategorySuper
_name='project.category.super'
_inherit='project.category'

Then on Project add relation Many2One to ProjectCategorySuper

And set as mandatory for any projects at the Form View level.
Also a good place to show such field could be after partner_id
And of course add search and group by.

module: project_closing
version: 8.0

Hi all,

I would like to as if you agree or not.

Project manager have access to project
Project manager doesn't have access to accounting

Sometimes projects manager create projects that after all must be deleted because are not need anymore. This projects have analytic account (aa) but doesn't have task nor activities.

When project manager delete the project, aa is still there.

Do you agree to improve functionality of this module to delete aa when its related project is deleted only in the case that aa doesn't have and journal?

Thanks

Error while installing module
` File "C:\Program Files (x86)\Odoo 10.0\server\odoo\models.py", line 1074, in _validate_fields
ParseError: "Error while validating constraint

Element '' cannot be located in parent view

Error context:
View project.task.form.materials
[view_id: 1049, xml_id: n/a, model: project.task, parent_id: 499]
None" while parsing file:///c:/Program%20Files%20(x86)/Odoo%2010.0/server/custom/project_task_materials/views/project_view.xml:5, near

project.task.form.materials
project.task

    <field position="after" name="work_ids">
      <!--Materials used-->
      <field name="material_ids" groups="project.group_tasks_work_on_tasks">
        <tree string="Materials used" editable="top">
          <field name="product_id"/>
          <field name="quantity"/>
        </tree>
      </field>
    </field>

  </field>
</record>`

module: project_issue_task
version: 8.0

Steps to reproduce

• Read description

    'description': """\
Support for the use case where solving an Issue means a Task should be done,
such as an on site visit, and a report must be made to document the work done.
This is a common scenario in technical field services.
The Issue form already has a "Task" field, allowing to create a Task related
to an Issue.
This module adds some usability improvements:
  * "Create Task" button on the Issue form [Wrong name]
  * Automaticaly Close the Issue when the Task is Closed [BUG]
  * Automatically Cancel the Task when Issue is Cancelled [BUG]
  * Make the Task also visible to all followers of the related Issue [BUG]
""",

Current behavior

• If you go to an issue you will see a button "Task Report" and not "Create Task", name is incorrect but funcionallity is OK? (Button creates a project.task)
  
• But if you close the task, the issue is not closed
  
• And if the issue is cancelled the task is not cancelled
  
• Task is not visible to all followers of the related issue

Expected behavior

• "Create Task" button on the Issue form [Wrong name]
• Automaticaly Close the Issue when the Task is Closed [BUG]
• Automatically Cancel the Task when Issue is Cancelled [BUG]
• Make the Task also visible to all followers of the related Issue [BUG]

I can not change the status of a task after consuming materials. It fires an exception: You can only delete draft moves.

Is there a way to reapply a newly created SLA to old issues in a project? There's no "Service Level" tab into the old issues... I need to apply the SLA's to these issues.

Thanks for your great work.

EDIT:

Just saw that after a change in an issue the new tab appears, but it would be better to have them all applied without making any change... Thanks in advice.

Hi,

Thank you for this great work. I am having trouble creating the "control date" at first setup of a new SLA.
As I can understand, this seems to be the exact same problem that the one reported in this issue : Can't setup "control date" #50.

To create a new SLA, I went throught these steps :

• Creating a project and working hours
  -Go to its analytic account form
  -In SLA part, when modifying, click on add new item
  -Then click on create
  -On the SLA form there is a "Control Date" field that is empty. When creating a new entry with all mandatory field fullfilled, click on save button leads to an error (popup) saying that the field "model" is invalid.

This field is not alterable.

I am sure I get there using the wrong path, but I cannot find another way.

I am using V8

Thank you for your kind response.

Can only be done by a member of the OCA organization.

Hi,

Add a shortcut in the kan ban view and in tree view that opens a wizard with the messages of message_ids component of project.issue. Almost like the behavior of the icon that opens mail editor on the same field (present on the form view). So users might not click on issue anymore to see the history of that specific item since I think the javascript loading will take more time than opening and closing a wizard.

It's actually a improvement that I think can help a lot in shorten time of issue or tasks attendance.

I view on log this WARNING:

openerp.modules.module: module project_task_code: no openerp.py file found

But the file is on folder. The perms are ok, ?¿?¿?

the recurring contracts backport have a bug - I think it's a bug - that it creates all invoices with currency set to Euro.

I tried this with many DBs and same result.

If i create invoices normally out of contracts I get the correct currency.

So only invoices generated by this module gets a fixed currency of Euro.

Some Details:

• OpenERP v. 7.0 latest stable build
• Module is account-analysis-recurring backport
• DB is empty from scratch DB without demo data
• Invoiceing installed & configured with US CoA / Service based business + currency other than Euro.
• contracts and recurring backport installed

Regards,

Hi,

I extracted the agile project modules of Vauxoo addons (https://github.com/Vauxoo/addons-vauxoo) to a new repo:
https://github.com/kmee/project-agile

There are also other good initiatives:

https://github.com/vertelab/odoo-project_scrum/tree/8.0
https://github.com/codoo/project-scrum

I wonder if it would be interesting to create a new project in OCA "project-agile" or make a PR in this repository.

Shouldn't be too hard, volunteers are welcome!

I'm finding this error in my server logs.
Still need to investigate further:

(...) ERROR openerp.addons.base.ir.ir_cron: Call of self.pool.get('project.sla.control').update_sla_states(cr, uid, *()) failed in Job 7  
Traceback (most recent call last):
  File "/home/odoo/openerp/addons/base/ir/ir_cron.py", line 138, in _callback
    getattr(model, method_name)(cr, uid, *args)
  File "/home/odoo/openerp/api.py", line 268, in wrapper
    return old_api(self, *args, **kwargs)
  File "/home/odoo-addons/project_sla/project_sla_control.py", line 117, in update_sla_states
    self.write(cr, uid, control_ids, {'sla_state': '4'}, context=context)
  File "/home/odoo/openerp/api.py", line 268, in wrapper
    return old_api(self, *args, **kwargs)
  File "/home/odoo-securitas/project_sla/project_sla_control.py", line 99, in write
    if doc.sla_state < new_state:
  File "/home/odoo/openerp/fields.py", line 841, in __get__
    return record._cache[self]
  File "/home/odoo/openerp/models.py", line 6076, in __getitem__
    return value.get() if isinstance(value, SpecialValue) else value  
  File "/home/odoo/openerp/fields.py", line 56, in get
    raise self.exception 
MissingError: ('MissingError', u'One of the documents you are trying to access has been deleted, please try again after refreshing.')

Odoo V8 has on account.analytic.account
'parent_id': fields.many2one('account.analytic.account', 'Parent Analytic Account', select=2),
Since V9 this feature disappear.

Module Project

parent_id = fields.Many2one('account.analytic.account', 'Parent Project')

Could be interesting have again this parent relation?

I have seen one explanation about the reason of this change:

• Using parent accounts (for financial accounts also) was removed in v9 because it mixes two concepts: (a) data and (b) how you want to consolidate/report the data. Odoo now uses TAGS to manage the concept of (b) instead of parent_id.

• Analytic Accounting reports that use these tags, which are more flexible and functional than parent_id's

Hi,

We setup a new server environment and installed project module and then installed project_sla module. below are error messages we got.

In client:

Invalid XML Architecture

In Server:
2014-10-08 08:40:54,505 25073 INFO project_oca openerp.modules.loading: module project_sla: loading project_sla_view.xml
2014-10-08 08:40:54,538 25073 ERROR project_oca openerp.addons.base.ir.ir_ui_view: :2:0:ERROR:RELAXNGV:RELAXNG_ERR_EXTRACONTENT: Element form has extra content: h1
2014-10-08 08:40:54,549 25073 ERROR project_oca openerp.tools.convert: Parse error in /opt/openerp/server/custom_modules/project_sla/project_sla_view.xml:21:

view_sla_form
project.sla

            <form string="SLA Definition">
              <h1>
                  <field name="name"/>
              </h1>
              <group>
                  <group>
                      <field name="control_model"/>
                      <field name="control_field_id"/>
                  </group>
                  <group>
                      <field name="active"/>
                  </group>
              </group>

              <notebook colspan="4">
                <page string="Rules" name="rules_page">
                  <field name="sla_line_ids" nolabel="1"/>
                </page>
                <page string="Contracts" name="contracts_page">
                  <field name="analytic_ids" nolabel="1"/>
                </page>
              </notebook>
              <button name="reapply_slas" colspan="2" string="Reapply SLA on Contracts" type="object"/>
            </form>

        </field>
    </record>

Thanks,

Have project.task link to unique category for statistic.

Create new class:
class ProjectCategory
_name: 'project.category'
_inherit: 'project.tags'

Inherit class:
class Task(models.Model):
_inherit = "project.task"

categ_id = Many2one('project.category')

Add menu to manage Category
Add on Form, Tree view, Search, Group by

Good to have:
Demo data

Todo

https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-9.0

Modules to migrate

• project_analytic_line_view
• analytic_hours_block
• project_recalculate
• project_baseuser
• project_issue_baseuser
• project_gtd
• project_categ_issue
• project_categ
• project_closing - by @lreficent - #278
• project_issue_task - By @cubells - #209
• project_issue_code - By @mikevhe18 - #204
• project_task_code - By @cubells - #206
• project_task_materials - By @cubells - #207
• project_task_materials_stock - By @cubells - #208
• account_analytic_analysis_recurring - Migrated as contract in https://github.com/OCA/contract
• project_service_type
• project_classification
• sale_order_project
• project_timesheet_analytic_partner
• project_sla
• project_stage_state - #283
• project_functional_block
• project_closing - #278

Modules to rename or deprecate

• service_desk - by @dreispt - #279
• service_desk_issue - by @dreispt - #281

Hi @dreispt , thinking and testing this module I would like to ask you opinion in my reflexions.

Installing this module is very specific and maybe we could make it better. I think that we can maintain this functionality better by adding 2 more security groups in project (setting -> Users):

• User
• Member (new group)
• Project Manager (new group - for res.user who are assigned in user_id in project.project)
• Manager

This way we don't touch Odoo's permission groups so if you don't user "member" or "project manager" you will have same functionality of Core.
#1

Employees are now basic Project users, able to create new documents (Issues or Tasks). These are kept editable while in New and Cancelled states, to allow for corrections or for the user himself to cancel an incorrectly created request. Previously, Employee users did not have any write nor create access to project documents.

• Adding to employees make all employees access to project (this is not very common), this is not good as many employees must see the minimum part of their job, just sales, just purchases, just accounting...
• Force to customer to use "New" and "Cancel" states, in fact, for to use states when Odoo v8 and v9 do not use it anymore.

I think we must maintain option in Setting -> User to select if a user or employee access to project o not.

Note: Odoo core has a functional bug in my opinion. By default a Project User cannot create issues... this has no sense. So we can add this to the default user's group. Project Users can create issues. Here is how you must add this manualy: https://youtu.be/ZLzZ-o6q8N0
#2

Project Users, on the other hand, are supposed to act on these documents, such as reported issues, and update them accordingly, so they have write access for all states. Employee users don't have write access on later states, but can still write comments and communicate through the message board (open chatter).

In general, users will only be able to see documents where:

They are assigned/responsible for, or
They are following, or
They are a team member for the corresponding Project (but not if only in the project's follower list).

Project's Members in project.project have same permission as Project's followers. This have many sense, as you have permissions on the project but you don't need to follow it. this has two benefits:

1. Project manager when creating task doesn't have to delete followers pulled from project.
2. Project users don't have see all task in one project, they can unfollow or follow as needed.
   #3

Project Managers have access rules similar to Project Users, but additionally can create new projects and can see all documents for the projects they are the Manager. As a consequence, Project Managers no longer have inconditional access to all Tasks and Issues, and will only be able to edit the definitions of Projects they manage.

This makes it possible for a Project Manager to have private projects that other users, Project Managers included, will not be able to see. They will need to be added as followers or team members to able to see it.

Public Projects and their documents are still visible to everyone. Portal users access rules are kept unchanged.

Adding "Project manager" groups (which is different of Manager) you will have same functionality as you describe. You can have many project managers who are independent of each other and you can still have a Full Manager like CTO, CIO or also CEO who see everything.
#4

Access Rules summary:

We will have in Setting - Users - Access Right - Application - Project

Employee Users Can see only documents followed or responsible for (in "user_id"). Can create new documents and edit them while in "New"/"Cancelled" states.

• User

Project Users Can edit Project Issues and Tasks in any stage/state. Can see all documents for projects they are followers on team members. Can see only documents followed or assigned to for other projects.

• Member

Project Managers Can create new projects and edit their attributes. Can see all documents (Tasks or Issues) but only for their managed projects. For the other Projects, will see only followed documents, just like the other users.

• Project Manager
• Manager

Note: For sure if needed we can add also "Employee" as you described, having 5 groups of permission for projects.

Also I think is more clear to understand for anyone.

After writting this I have read #59 so welcome @jbeficent

We can do this of v8 like I described if you agree.

@dreispt could be this and [IMP] of project_baseuser of it must be a new one.

cc @antespi @pedrobaeza

On service management use cases we can have Service Contracts, and for these you may want to identify the Service Items covered by the Contract.

Current status

Currently the OCA/project already supports these concepts:

• Service Contracts are modeled as Analytic Accounts.
• Service Items can be represented as child Analytic Accounts.
• Service Requests/Orders can be represented either as Project Tasks or Project Issues.
• Service Desks are where the end users will place their requests. These are represented as Projects and should have a user/customer oriented organization.

The need

In non trivial setups we also need a Service Company or Department, identifying who should provide service on a Service Item or Contract.
It's possible that this service is be outsourced to a supplier/business partner, or provided internally by an employee or department. Scenarios with both cases are not uncommon.

Proposed design

I propose to add to "Analytic Accounts" (thus to Service Items) a new "Service Partner" field, linked to a Partner record.

It can represent an external company or person, or an internal employee or team/department.
In the last case we might need to artificially create a Partner record for the employee or team, but would be the price to pay to avoid a more complex design.

In the first case we may create several Contact Partners under the same parent Company Partner, to represent different branches or technical practices:

• depending on the Service Item's address, in can be serviced by different branches/offices of the servicing company;
• depending on the Service Item's technology, it can be serviced by different specialist teams of the same servicing company.

Also adding a a "Is Service Provider" flag to Partners would make it much easier for service managers to maintain their Contracts mater data.

The Service Partner should be copied to the Service Request (issue or Task) when selection the Service Item, for auditing purposes and for enabling business rule automation, such as assigning responsible users or sending out notifications.

Going further

With this we can assign a Service Partner individually to each Service Item, but that maintenance task could be simplified by using a matrix, to automatically pick a Service Partner depending on Service Item attributes: geographical localization (Service Area), technical Type, and maybe others.

This is compatible and would extend the proposed design, but is out scope for this bleprint.

project_issue_automatic_workflow will provide the ability to configure custom actions on project.issue:

• Change states
• Post message
• Post internal message
• Change priority
• Change assignee
• Add follower

based on events:

• Create/Write
• Message received
• Inactivity

with some conditions:

• If in stage(s)
• If event is triggered by a customer, vendor, and/or employee
• If last message was customer, vendor, and/or employee

This should allow for a nicely configurable Service Desk without the need to make server actions.

Does anyone know anything we can start with here, or have any cool ideas?

I traced it to project_sla_control.py, function _compute_sla_date().
Maybe I'll fix it when porting to the new API.
The workaround is to ensure a Working Calendar is set for the SLA controlled Projects.

Should be:
if not default.get('timebox_id', False):
default['timebox_id'] = False
if not default.get('context_id', False):
default['context_id'] = False

One of the major things keeping me from migrating my PM from JIRA into Odoo is the lack of agile functionality. This RFC is a planning/call to arms to solve a problem that we are all likely having.

There are basically two types of agile, so I see there being two base modules:

• Scrum - Sprint based development
  • Sprint opens with a planned end time
  • Only active sprint is displayed to users in non-planning view
    • Let's forget about the planning view for the moment though, that's a whole different nut to crack
  • Sprint closes, open cards are moved to next Sprint in sequence
  • Next sprint in sequence is moved to active
• KanBan - Release based development. Sucks that this name clashes with Odoo's, so we'll probably just call it Release
  • All open issues are displayed to users
  • Release closes, closed cards are moved from active view and tagged to release

The reporting is very different between the two, but we can worry about that later. I'm wondering if we have anything that sort of fits these requirements already? They're fairly high level at this point in order to try and be as open minded as possible in regards to actual workflow.

Hi,

Just installed the project_sla in Odoo 8 but I can't see things working. In your setup checklist from the openerp.py file I can see that "Working Calendar" must be set into Project's "Other Info" tab. Where is that "Working Calendar" or what do you mean? I don't see it...

When I create a contract, with it's project and I link a SLA to it, every issue I try to create in the project just keeps the server loading. It's like everything related with a SLA won't work.

P.D: had an error in project_sla.py with 'control_field_id' domain. ('type','in',['date','datetime']) did not work, for my instance (don't know why) 'type' field was named 'ttype' in ir.model.fields model.

Thanks

I have installed the timeline and web_timelin modules, however I keep receiving the following error when I select the view. I have tried deleting all tasks, and I then can slect the view and have an empty view, however when I insert 1 task, I receive the error again.

I have tried to install as many of the project modules as required, but still no joy.

Error:

Expected ';'
http://10.0.0.224:8069/web/content/1337-d77a06b/web.assets_backend.js:6823
Traceback:
SyntaxError: Expected ';'
at Anonymous function (http://10.0.0.224:8069/web/content/1337-d77a06b/web.assets_backend.js:6823:36)
at _.forEach (http://10.0.0.224:8069/web/content/528-c8ce360/web.assets_common.js:12:558)
at event_data_transform (http://10.0.0.224:8069/web/content/1337-d77a06b/web.assets_backend.js:6823:1)
at Anonymous function (http://10.0.0.224:8069/web/content/1337-d77a06b/web.assets_backend.js:6826:1142)
at _.forEach (http://10.0.0.224:8069/web/content/528-c8ce360/web.assets_common.js:12:558)
at on_data_loaded_2 (http://10.0.0.224:8069/web/content/1337-d77a06b/web.assets_backend.js:6826:1085)
at Anonymous function (http://10.0.0.224:8069/web/content/1337-d77a06b/web.assets_backend.js:6826:922)
at Anonymous function (http://10.0.0.224:8069/web/content/528-c8ce360/web.assets_common.js:547:661)
at fire (http://10.0.0.224:8069/web/content/528-c8ce360/web.assets_common.js:541:278)
at self.fireWith (http://10.0.0.224:8069/web/content/528-c8ce360/web.assets_common.js:546:198)

On project_categ

Already have task_categ_id and mean to set a root Category for Tasks linked.

So on Task could choose only Tags which parent is the root Category on Project.

Our concern is to have one unique category on Project that mean to categorize for which kind of Operation is.

For this on
project.categoy we think to add boolean is_business_category
add constrain to prevent have duplicated name if is_business_category

Add on project.project
project_category_id many2one project.category
On Form View: should be required
ACL to be discuss
Group by
Search

Todo

https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-10.0

Modules to migrate

• analytic_hours_block
• project_analytic_line_view
• project_baseuser
• project_categ
• project_categ_issue
• project_classification
• project_closing - By @Jerther - #271
• project_description - By @astirpe - #203
• project_double_alias - By @pedrobaeza - #305
• project_functional_block
• project_gtd - By @mmequignon - #308
• project_issue_baseuser
• project_issue_code - By @thinkwelltwd - #244
• project_issue_task
• project_issue_timesheet_time_control - By @luismontalba - #269
• project_recalculate - By @pedrobaeza - #291
• project_service_type
• project_sla - By @OpenCode - #361
• project_stage_state
• project_task_code - By @kellylougheed - #213
• project_task_default_stage - By @astirpe - #201
• project_task_materials > project_task_material - By @chienandalu - #251
• project_task_materials_stock > project_task_material_stock - By @cubells - #288
• project_timeline - By @carlosdauden - #297
• project_timesheet_time_control - By @luismontalba - #266
• project_timesheet_analytic_partner
• sale_order_project - By @Abranes - #377
• [ ] service_desk (#174 must be refactored in 9.0)
• [ ] service_desk_issue (#174 must be refactored in 9.0)

I'm just wondering if I can change the initial date that makes the hours calculation (by default is doc.start_date) because our employees, sometimes, create the issues after resolving it but filling in a datetime field called "Issue started at". I'd like to change the initial date to that field...

By just making this change into the project_sla/project_sla_control.py would it be possible (line 198)?:

start_date = dt.strptime(doc.[my_date], DT_FMT)

Would I need to make any other change to achieve this?

Thanks

@dreispt I'm interested to use this module. However I have the following concerns:

• If the group "Project Manager" can only view the projects they manage, why can they still access to the project configurations settings for all projects?
• Who will then have access to view all projects? I can see that in an organization, directors will need to have access to list all projects.
• In an organization that has a Project Management Office administrative department, a PMO Project Administrator role would typically have full access to all projects and also Project Configuration, because they provide service to all Project Managers in the organisation.

Would it make sense to add the following changes?

1. Add a new group "Project Administrator", that has full access to all projects + access to the Project Configuration menus.
2. Remove the authorisations to the group "Project Manager" to access to the Project Configuration menus.

Regards,
Jordi.

The service_desk module name relates to what it wants to achieve, but not to what it does.
It should be replaced with more meaningful modules.

The intended approach is to reuse Projects and Issues, and adapt them to better fit the need for service management. For this, Projects represent Service Areas and Issues represent support cases/tickets.

Service app

Modules for service management specific feature should have a service_ prefix in the name.
The base module for this should provide a "Service", with a new top menu, and menu options for Service Areas and Cases.

Projects should have a flag to identify Service Areas from regular Projects.
Followers are to be used for the teams to be notified on cases for their service areas.

An improved security model for end users is also needed.
Discussion took place on #108 and is implemented by #117.

Additional record access controls are also needed for Service Areas - users must be limited in what areas are available to them, Some areas, such as related to second line support, should be available only to certain support teams. Service Areas could have a list of Security Groups that are allowed to see them.

It would be good to allow for teams/groups to subscribe Service Areas, rather than only partners.
In fact v9 already supports that, through Channels. But for v8 it is an open issue.

Service contracts

A support case can/should be related to a Contract (an Analytic Account).
This is implemented by service_desk``service_desk_issue and should be extracted from there.

Service locations

For scenarios involving field service, the service location is also needed, maybe required.
This is bundled by the implementation in service_desk``service_desk_issue and should be extracted from there.
There is space to expand and improve such implementation, to support identification of service sites, service items, and the type of services contracted for each, but that deserves it's own discussion.

Support Cases

Many interesting features can be added to Cases.
Here are a few:

• Case number sequences (see also project_task_code)
• Duplicate of and Duplicates list
• Related cases list
• Sub-cases: to assign activities to several people/teams
• Case Reopened counter, for quality statistics
• Add Diagnostic questionnaire
• After service customer satisfaction survey
• Affected component (based on component tree; this is a complex requirement - see Service Locations)
• Cause of problem / Resolution categorization

Hello,

We've installed the project_timeline module which install the web_timeline module too !

It works but all the modification are not kept cause of an sql error !!

Is it a bug or a config problem ?

Note that our timezone is "Europe/Brussels".

Thanks for your help.

bad query: UPDATE "project_task" SET "date_end"='2017-07-19 22:29:09',"project_id"=13,"date_start"='2017-07-19 21:36:00',"write_uid"=6,"write_date"=(now() at time zone 'UTC') WHERE id IN (31)

Don't show the view.

I am working on a module to create and link tasks from RMA claims and I was thinking about also taking into account materials for deliveries and possibly repairs.

RMAs are related to pickings, but the module project_task_materials_stock links to moves, so any ideas on how to make it simple are welcome.

The materials to add to the task would be the products in outgoing pickings (checking with self.env.ref('stock.picking_type_out').id).

I have to improve the code quite a bit but I'm already working on the PR I'll soon link.

Thanks for any help or opinion you might add here!

Hi, are the modules already fully ported to v8 or is there still work to do? Do you need help with the migration effort? We might need them for a client of ours.

Thanks

As an IT Manager/Director, I need to oversee the status of my ongoing projects, in order to periodically report to stakeholders.

A key output is a grid with the active Projects, a very short status summary, and the progress over the X last reporting periods.

At this point, "progress" can mean just a short free text description the stage/phase the project in.
Later improvements could make the current state a Many2one field, and add some KPIs (% complete, risk traffic-light sign) .

Proposed design

• Add to Projects a "Status" notebook tab, with fields: Status Date, Status Summary and Status Description.
• Writing on these fields will trigger a write on a Project Status History table. If there is already a record for the Status Date, it will overwrite the existing data.
• A view bases model should be provided for dashboard/reporting purposes, mapping the status lines against a timeline (similarly to "project.task.cumulative").
• In the corresponding Pivot view, the user can choose the period of the reporting: monthly, weekly, daily...

Customer's project reports

Hi, (I open this discussion here because we must mix functional and technical skills to specify and develop a good module).

Maybe I mistake project in Github and there is another better.

Why this module?

I need to develop a module to satisfy requirement of my customer, but I prefer to discuss here the functionality and fit this to my customer than develop my customer's need and after that try to send this to OCA.

The only report I have seen from @dreispt about this is here described: http://www.slideshare.net/dreispt/service-management-at-securitas-using-openeerp, and is a very specific one.

I guess even thought clients want a specific report we can have a general use one which is the base of the rest.

Note: As this is for reporting you client some one can expect reports in account.analytic.account (Contracts) and account.analytic.line ("Invoice task") but this is not the case.

What we have:

• We have project
• We have project.task
• We have project.task.work (here is the real time dedicated)
• We have project.issue

Which variants of report could we need:

• Report of all tasks works (project.task.work) of a single customer from a group/single projects.
• Report of all project issues (project.issue) of a single customer from a group/single projects.

Requirements:

1. Report must contain this information:

** Header

• Customer (from tasks)
• Project (could be more than one so we must select them in a Wizard)
• Range of date of the report (we must select in a Wizard from/to dates in project.task.work)
• Planned hours (from tasks)
• Effective hours (from works)
• Remaining hours: planned minus effective

** Body

• List of all works with date, description and hours
• List of all issues with date, name and hours
  • group by client (with totals)
  • group by project (with totals)
  • group by task (with totals)

2. Wizard:

• Select dates, from / to
• Select Customer
• Select Projects (if empty it will take all tasks of this customer)

Let see who is interested in and get some more ideas.

Check https://github.com/serviciosbaeza/serviciosbaeza-odoo-addons/tree/8.0/project_task_work_print from @pedrobaeza

There is not even a action_close anywhere on other modules

Is there a way to configure the system to consume material from different locations depending on the user completing the task? (eg. create a WH location for each service truck and remove consumed materials from user's truck instead of main WH stock location)

Currently CI build fails because of a missing dependency:

ERROR: "You try to install module 'project_action_item' that depends on module 'hr_timesheet_task'.
But the latter module is not available in your system."

Is this dependency avoidable?
Otherwise we need add the corresponding repo to the TravisCI config.

Good afternoon!
I have all the necessary rights .
But when I try to create a project , I get the error :
except_orm: (u'Access Denied ', u'The requested operation can not be completed due to security restrictions Please contact your system administrator \ n \ n (Document type:.. Project, Operation: create)')
Creating a project is only possible by the user admin.
Please, help.