nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to clear Request Type when converting a request to a sub-task

James Murray_w0r1kc

In JSM, when we convert a Request to a sub-task, the Request Type field in the sub-task is populated with that of the initial Request with red text and an error message around it.

Screenshot 2024-11-11 at 9.14.29 AM.png

How do we clear this out as obviously a sub-task doesn't have a request type and the red text looks bad.

Thanks,

James

Accepted answers

Marc -Devoteam-

Hi @James Murray

First of all, why are you converting, this will mean the reporter of the request can't follow the request in the portal anymore.

Best practice is, if work is required to no be visible on the portal, based on the request), create a sub-task under the request.

All comments

Manoj Kumar Gangwar

Hi @James Murray welcome to the community!

You can create an automation.

Trigger: Field Value changes ( select Issue Type)
Condition: Issue Type is Sub-task
Action: Edit Issue > Set field "Request Type" to blank

Marc -Devoteam-

Hi @James Murray

First of all, why are you converting, this will mean the reporter of the request can't follow the request in the portal anymore.

Best practice is, if work is required to no be visible on the portal, based on the request), create a sub-task under the request.

James Murray_w0r1kc

Thanks @Manoj Kumar Gangwar , I tried that but unfortunately it doesn't allow me to edit the Request Type like this:
Can't edit.png
If I then use the Edit request type action then it won't allow me to leave it as blank:

Screenshot 2024-11-11 at 9.43.09 AM.png

Could you show me your automation and how you were able to achieve this. Maybe I am missing something.

Thanks,

James

James Murray_w0r1kc

Understood. This is for an internal help desk and the requester has the ability to see sub-tasks also. It is just part of our workflow.

The feature exists to convert to a sub-task and it does work for us. We just need to get the request type cleared out.

Marc -Devoteam-

Hi @James Murray

On converting an issue to a sub-task the trigger in an automation can't be the Field Changed based on issue type as the convert action doesn't trigger an automation rule.

See, JSWCLOUD-22432

So your automation should trigger on something else defined in the converted issue, or use a manual trigger.

The edit should be an advanced JSON

Example rule, with edit to clear Request Type:

Screenshot 2024-11-12 at 11.13.16.png

James Murray_w0r1kc

Thanks Marc, I will give this a try!

James

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management