If you want to perform the same action on multiple requests of the same type, you can use the mass request update feature to do it. Just search for requests of a given type, and then update the entire set of requests at the same time instead of updating each individual request.
Following are some examples of situations in which mass updates are useful:
A development manager searches for all new defect requests. He wants to assign 20 of them to the same developer. This involves updating the Assigned To field on all 20 requests, and pushing them from New to Assigned status.
Fifteen requests are currently assigned to you. Because you are going on an extended vacation, you need to reassign all of these requests to another engineer.
You need to add the same specific stakeholders to escalations from a particular customer account so that management can be copied on emails generated by activities to these escalations.
You can quickly and easily handle cases such as these by mass request updates.
The mass update feature is enabled by default. To disable it, set the server configuration parameter
true. For more information, see the Demand Management Configuration Guide.
Caution: Do not use PFM - Finish Period by Month validation for non-PFM-Proposal request types. An error occurs when performing Quick Edit or Mass Update on requests of non-PFM-Proposal request types that use PFM - Finish Period by Month validation. This is because the PFM - Finish Period by Month validation requires a field with token KNTA_PLAN_START_DATE for the SQL to be executed, while for most of non-PFM-Proposal request types, there is no such field.