Project and Portfolio Management Practitioners Forum
cancel

Renaming a Request

Highlighted
Tracy Crawford
Regular Contributor.

Renaming a Request

What is the best process for renaming a request type in production? I know that if you migrate a request to production, it sees it as a new request. Is it best to rename the request in production first, then migrate the renamed request into production?

Thanks!
5 REPLIES
Tracy Crawford
Regular Contributor.

Re: Renaming a Request

I forgot to mention. I want to rename to it's original name. For example, the original name is 'ABC - Request'. The request got updated and moved into production with the name 'ABC - Request (New)'. I want to name it back to 'ABC - Request'.

There are still outstanding request of with both names.
Mahen M
Acclaimed Contributor.

Re: Renaming a Request

Hi,
All the Request Type Operations happen through 'Request Type ID' and not through 'Request Type Name'.

I hope you can change the name directly in Production without any issues. I have done in the past.

Thank you.

Regards,
Mahendran M
Mahen M
Acclaimed Contributor.

Re: Renaming a Request

"Is it best to rename the request in production first, then migrate the renamed request into production?"

I hope the ave statement should be like the one below

"Is it best to rename the request in QA first, then migrate the renamed request into production?"

If you do like this... then the Renamed request type in QA will move as a new entity into PROD.

Thanks

Regards,
Mahendran M
frank chiang
Valued Contributor.

Re: Renaming a Request

Try to rename the one in Production with a version number (i.e ABC - Request v1.1), then migrate the latest version to Production with its original name.

You might also want to check for any porlet or query or customizations that reference to the request type name "ABC - Request" because you now have to take into account for all request types like "ABC - Request%".
Tracy Crawford
Regular Contributor.

Re: Renaming a Request

Thanks! I'll give it a try!