Proposed Evolutions

1) If several activities (connected by a "parent") => Request (like copying) to remove the entire structure

2) Same for a project (activities, milestone, structure ...)

3) Change the combo box "project" views activities, project milestone, ... that which manages the project (top left). Objective: To limit the list of proposed projects

4) When you created a ticket is necessary to save before you can add an attachment, in the future it may be more efficient to be able to upload attachments before saving

5) Via assignment, you can assign the same person twice on the same task. This can cause to errors ...

6) When changing an activity structure project, the new project is not affected stain girls activity => Inconsistencies on monitoring.

In all objects (Ticket, action, project, risk ...) it selects the project with a combo box that lists all projects in the database including those that do not see the CDP. For me it impacts 2:
- The selection is more complex (thank you for the improvement of V3.1)
- A contact (customer) also see the list of all projects managed by the company ....
If we replace the combo box of objects with "Project Combo Box" that filter the list according to rights

If you change the parent activity of the project, sub-activities are not assigned to the new project