![]() ![]() Of course, they can provide missing information in a comment, but people are used to communicating with support teams via email because they see it as a safer way of passing on the important messages. Simple editing or option to give feedback may have a great effect on the user experience. Changing only the workflow statuses visible on the request view won’t We need to give the customers some control over the request on the detail view. ![]() Changing only the workflow statuses visible on the request view won’t enable it. The first thing to remember is the customers want to cooperate with us. This way, the statuses on the Request Detail View will be suitable for the request type the client is using. Or when the customers raise a request to book a room, they will see Booking requestedstatus instead of Open or Booked when the request is done. For example, when we have the same request types in 2 different languages and want our statuses to be understandable in both. Of course we can create custom statuses in the workflow editor, but then their names will be restricted to the issue type, and sometimes we will need them to differ for actual request types. To do it, we need to go to Request Types in Project Settings, choose Edit fields of the request we want to modify, and click the Workflow Statuses tab. Just like we provided display names for fields on the request form, we can name each workflow status on a given request type. The only out-of-the-box customization we can do natively in Jira Service Management is to change the names of workflow statuses visible for the customer.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |