Rename, retire and delete
Three different actions with three different outcomes — and which one keeps the history.
Which one do I want
| Action | History | In the picker | Condition |
|---|---|---|---|
| Rename | Kept | Under the new name | The name must not be empty |
| Retire | Kept | Absent | Always possible |
| Delete | There is none to keep | Absent | Only when it is entirely unused |
Renaming does not change the identifier
A service's or line's technical identifier never changes after creation, however completely the name changes. That is why old links and reports do not break.
Renaming a service updates the titles of engagements that have no title of their own. An engagement you titled yourself is left untouched.
You usually want retire, not delete
A retired service leaves the picker but all of its past engagements stay exactly where they are and remain in reporting. It also drops out of the active service count.
Retiring a service line takes its services out of the picker as well.
Delete is only for what was never used
A service with engagements attached will not delete, and neither will a line that still holds services. Services first, then the line.
It is the same rule as everywhere else: something with real work attached does not quietly disappear.
Read this next
- Service catalogueBuild your catalogueStart from one service line, not from an org chart.
- When something does not workA delete was refusedThe refusal names every holder at once. Start there.
- Pipeline & opportunitiesRename the stages for your firmPut the stages into your own business vocabulary without breaking reporting.
Still stuck?
If the answer wasn't here, write to us. It is a real inbox and it gets answered.