Urgency, Impact, and/or Priority field in a Service Catalog item

To me its important that priority can be used flexibly in order to take context into account, and not just have services, CIs and e.g. people logged in the same way every time. At time of logging its also important as this might be high priority in context but set at low priority as a default - so a high priority incident might not get escalated or noticed in an appropriate time, as it is only logger as low priority.

Service management requires the ability to understand people and business needs and manage these in context...

I’d like to see service requests have additional functionality around fields, which would provide for the request above.

It would be useful if, in addition to the current service request field design, it was possible to configure fields to appear on a section on all service requests. Would be useful if this could include standard ticket fields, such as urgency, impact, priority etc, plus custom fields that have been added for tickets.

Would save having to add an “urgency” field to each and every service request item then and it wouldn’t require workflow to set that on a ticket when raised.