Renaming project tasks leaves remnants of old name
Bug #1186960 reported by
Marcel van der Boom (HS-Development BV)
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Odoo Addons (MOVED TO GITHUB) |
Confirmed
|
Low
|
OpenERP R&D Addons Team 1 | ||
Bug Description
When a summary of a project task is renamed some remnants remain of the old name. For example when a notification for that task is generated, the name of the task displayed in the inbox is still the original name.
I've added a little screen-recording to clarify.
Related branches
Revision history for this message
| Marcel van der Boom (HS-Development BV) (mrb) wrote | #1 |
| description: | updated |
| Changed in openobject-addons: | |
| assignee: | nobody → OpenERP R&D Addons Team 1 (openerp-dev-addons1) |
| importance: | Undecided → Low |
| status: | New → Confirmed |
Revision history for this message
| Marcel van der Boom (HS-Development BV) (mrb) wrote | #2 |
| tags: | added: project |
To post a comment you must log in.
This probably deserves a higher priority than low? Having two names floating around in the system for the same task is confusing and embarassing in the invoicing stage.
There is a branch linked which seems to fix the issue, is there a reason this can't be merged?