Using request type name in atomation rules

[Alexey Paveliev]

Hello community,

I add a static text prefix to summary by using Edit issue action with the value:

• whatever text I add  {{issue.summary}}

Has anyone figured if the name of the request type can also be used as a value?

So if user create a ticket of type "Create new user" with a random summary, the rule would add "Create new user" to that summary

[Lucas Knorr · Accepted solution]

@Alexey Paveliev I want to mention another way of approaching your requirement.

Are you already aware that you can provide default values in a request type? 

If you want to stick to your current way. You can use this smart value

{{issue.Request Type.requestType.name}}

to receive the request type name. 

[Alexey Paveliev]

@Lucas Knorr thanks a ton.

The smart value you provided worked. That's what I was looking for!

I knew about the hidden values and we use them a lot, but it would not work for the case at hand

[Jakub Cieslak]

Hi, I am not sure if I got it right, but if you are looking for a smart value that will print the name of the Issue Type, you can use this one:

{{issue.issueType.name}}

[Alexey Paveliev]

nope. Request type is not the same as Issue type.

If I use what you provided I get "Task" not the "User Access" or whatever a type service management is configured to have