Before this commit, when the user edits the description of a task with use_pad=True and then change the project of this task to one with use_pads=False. The description written in the pad server is not copied in the description field of the task. This commit copies the content of the pad for this case when the use_pad changes to become False and description_pad is set. Step to reproduce: ----------------- 1. Go to Settings of the Project App and enable the Collaborative Pads 2. Go to the Project App, in the Projects dashboard (kanban view of projects) 3. Create two Projects (one called "Project A" and the other called "Project B") 4. Edit the Project B to activate the pad, that is, check the Use collaborative pads checkbox. 5. Go to the view list of tasks in the "Project B" 6. Click on "Create" button to create a task in the task form view. 7. Write a description for this task. 8. Change the project of this task by the "Project A". With this change, the collaborative pad is disabled for this task since the Project A has not the pad, and then the description field is empty rather than have the content that we have just written. task-2515150 closes #70401 closes odoo/odoo#70901 X-original-commit: 32a8f598d6a958f2a08b204524007cc075697fda Signed-off-by: LTU-Odoo <IT-Ideas@users.noreply.github.com>
Multiple UI and UX changes taskid: 2299401
Done the below several improvement on project: - move the stage description and tooltips to the debug mode - remove the 'need assistance' tag - Change the app description in manifest file 'Organize and plan your projects.' - Change the burger menu sequence into: Edit/Delete/Share/Set Cover Image - change the description of the pad feature into, 'edit tasks description collaboratively in real time. see each author's text in a distinct color.' - add the following tooltip for the allow_billable field, 'invoice your time and material from tasks.' - add an fa-stopwatch icon in front of the Start & the Stop buttons in task's form view - rename the 'validate time spent' modal into 'confirm time spent ' + increase the size of the description field + this field should not be required - project overview: rename 'Hours recorded' into' Recorded Hours' - project form view: disable the creation for the portal users field - Rename the 'ready for next stage' kanban state into 'Ready' TaskID: 2232051 Related Enterprise PR: https://github.com/odoo/enterprise/pull/9961 closes odoo/odoo#49694 Closes: #49694 Related: odoo/enterprise#9961 Signed-off-by: Yannick Tivisse (yti) <yti@odoo.com>
When the 'collaborative pads' option is activated for a project, and the visibility is set to 'portal users', it is possible to define the access level to pads to edit task descriptions. - If set to 'internal users', the behavior stays the same. - If set to 'portal users', a portal user has access to a pad to edit task descriptions on the portal. When configured for portal users access, by default, the task description is displayed with an 'edit' button on top of it. On 'edit' button click, the page is re-rendered with an additional url parmater 'edit=1' to switch to edit mode. In edit mode, the task description is shown in a collaborative pad, with a 'Save' button on top of it. On 'save' button click, the page is re-rendered with the 'edit' url parameter, to switch in classic mode (read-only). TaskID: 2204379 [IMP] project: collaborative pads in portal In order to be (easily) able to add buttons to the right of the description title, the description title is put inside a d-flex div. closes odoo/odoo#46591 Signed-off-by: Yannick Tivisse (yti) <yti@odoo.com>
Purpose fo the task is to improve the UX of timesheet, project and task. Done the chages for below point: - improve the stage demo data to unified the project stage - on the task timesheet 'sub-tasks hours spent' should be clickable and on click, it will display the list of subtask timesheet. - display in warning tasks for which Remaining Hours < 0 if Planned Hours > 0 in task list view - improve the settings of collabrative pad and planning and project form view Task-2129052 closes odoo/odoo#41092 Closes: #41092 Signed-off-by: Yannick Tivisse (yti) <yti@odoo.com>
Task creation was crashing when there was no project selected in the kanban's quickcreate window. closes odoo/odoo#41006 Taskid: 2146564 Signed-off-by: Yannick Tivisse (yti) <yti@odoo.com>
Purpose of this commit is to give description more "business oriented" because those descriptions appears in Odoo Studio which is supposed to be used by end users, not only by developers. Related Task ID : 37311
Due to the side effect on related fields that are not readonly, the value is saved in project although not changed. Putting it readonly avoids the problem. Fixes #26156 Closes #26171
The duplication of a task crashes at the following:
`content = myPad.getHtml(path).get('html', '')`
The copy mechanism is quite cumbersome:
- In `copy` method, generate an URL of a pad which doesn't exist since
`object_id` is still undefined.
- The `create` method somehow attempts to fill in the previously created
pad thanks to `_set_pad_value`.
The logic is made simpler. The pad URL field is set as `copy=False`,
therefore the create mechanism will take care of handling the pad
creation and its synchronization.
opw-1818757
Purpose ======= Currently if a project doesn't use pads, the created and duplicated tasks will initialize/copy them. That could be a real issue when migrating customers if we create a task for all the existing issues, since the models have been merged. Specification ============= Avoid this falsy behavior. We're forced to crappy fix with a context key as the project.task model 'inherit' from pad.common.