You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Hi everyone, I have one issue type with two Request types connected to it. This is working great, but there is one field where if its using a certain request type its pretty obvious what its going to be.
For example if its a "Hardware Request" then I have a field with hardware/software/etc I could just pre-fill that with Hardware instead of getting the agent to do it. But I don't want the field to be default entirely as it will always show hardware even on a software request.
Not sure if I'm missing something, or it is an automation thing. I do have a feeling I may not exactly following the process (as in might as well get rid of hardware/software field if we have that separated in request type) but it sort of has other uses (including reporting) so was hoping to keep it.
sure this is possible, for a specific Request type you can preset a value for a field (or more than one if you like). When configuring the Request form and you add the field you can select the value you want.
In the example below I used the Priority, but you can do the same with other fields.
I hope this helps
I agreed with @Giovanni Melai suggested. When one configure the request type form, one can pre-populate the field with a default value.
Another suggestion for you if the field in question is only for a specific request type, but it is not needed for another request type, then you should not have the field added to the second request type form.
Hope this also helps.
Best, Joseph Chung Yin
Jira/JSM Functional Lead, Global Technology Applications Team