Feature #7844
closed
Removal of COD acronym
Added by Krakowian Malgorzata over 9 years ago. Updated over 8 years ago.
50%
Description
Dear developers
I would like to ask you investigate in which places COD acronym is used in Ops portal.
We would like to remove it but first we need to understand how many places needs to be changed.
cheers
Malgorzata
Files
| ops portal ROD.zip (1.1 KB) ops portal ROD.zip | Krakowian Malgorzata, 08/22/2014 12:30 PM | ||
| ops portal COD.zip (1.67 KB) ops portal COD.zip | Krakowian Malgorzata, 08/22/2014 12:30 PM |
Updated by Lequeux Olivier over 9 years ago
- % Done changed from 0 to 50
If we want to change everything it will be awfull. We can plan to only change the interface part and not internal code labels even if that seems really not comfortable for me.
Some values like community ans helpdesk identifier are both internal and used in the code.
Could be critical, we have to discuss more about that, that could force us to update existing tickets which is not a easy part.
URLs and Interface :
--------------------
- Name of the tool
- Name of component CODTicket, CODNotepad, CODItem > tables/menus/urls/titles
- Helpdesk identifier
- Community
- ticket templates
- menus
Code :
------
- Internal community, heldesk identifier for notepads and tickets
- tickets workflows name and steps
- ton of classes and symfony components
- lavoisier views, and parameter view
Updated by Krakowian Malgorzata over 9 years ago
Lequeux Olivier wrote:
If we want to change everything it will be awfull. We can plan to only change the interface part and not internal code labels even if that seems really not comfortable for me.
Some values like community ans helpdesk identifier are both internal and used in the code.
Could be critical, we have to discuss more about that, that could force us to update existing tickets which is not a easy part.
I think what useful would be to have when possible is change of the templates.
This is what will have us now because we need to change templates every time we create ticket.
Other changes (Interface) would be nice to have one day but are not crucial because it doesn't influence usability - this is more a make up and cleaning.
cheers
Mal
Updated by Lequeux Olivier over 9 years ago
- Status changed from New to In progress
Well, if we start with templates it's (now ;-)) really easy.
Could you tell us exactly what are the modifications expected ?
cheers
Olivier
Updated by Krakowian Malgorzata over 9 years ago
Lequeux Olivier wrote:
Well, if we start with templates it's (now ;-)) really easy.
Could you tell us exactly what are the modifications expected ?cheers
Olivier
Do you have a list of message templates used in dashboards?
cheers
Mal
Updated by Lequeux Olivier over 9 years ago
Yes of course :
Here for COD dashboard, you will find all the "ticketing systems" and templates for each step :
https://svn.in2p3.fr/operations-portal/trunk/apps/frontend/modules/codDashboard/config/Workflows/
Same thing for ROD dashboard :
https://svn.in2p3.fr/operations-portal/trunk/apps/frontend/modules/rodDashboard/config/Workflows/
I know there is a lot of steps but this is the price of flexibility
Updated by Krakowian Malgorzata over 9 years ago
- File ops portal ROD.zip ops portal ROD.zip added
- File ops portal COD.zip ops portal COD.zip added
Hi
Attached those email templates which needed change.
I've kept "COD" word where it referred to part of the interface - they will need change when you change interface.
After the change please treat this ticket as low priority and we will come back to it when you will have time to finish it. 
thank you!
Mal
Updated by L'Orphelin Cyril over 9 years ago
- Tracker changed from Task to Feature
Updated by L'Orphelin Cyril over 8 years ago
- Status changed from In progress to Resolved