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; } } }

Unable to edit sub tasks

Sam Thornton_vntjui

Hello!

We're currently creating sub-tasks from forms that customers have submitted from the customer portal, and these sub-tasks are assigned to engineers to fulfill the request.

Whilst creating the sub-task is successful, we're unable to edit the sub-task, as I get the below error:

Request types can't be added to sub-tasks, so I'm unsure where to go from here?

Any help would be hugely appreciated.

Thanks!

Accepted answers

Sam Thornton_vntjui

The answer that helped me with this issue:

Create a new sub-task screen (without adding the customer request type to the screen)
Create a new sub-task screen schema and associate that with the new screen
Configure the Configure Issue Type Screen Scheme for sub-tasks, by adding the new screen schema to the sub-task issue type.

Sub-tasks are now editable without an error.

All comments

Esteban Diaz_qkbhq1

Hi @Sam Thornton ,

There is no way to relate a Request Type with a subtask Issue Type.
And subtask are not available on the portal, I mean Customers can not access to subtasks

Yo can only create standard Issue Types from a Request Type exposed in the portal.

At this point my question is: why do you need to relate a Request Type with a subtask ??

Cheers,

Esteban Diaz
https://www.linkedin.com/in/estebandiaz/

Sam Thornton_vntjui

Good Morning!

Thank you for getting back to me!

I didn't want to associate sub tasks with request types, it was more of a question of how to stop sub-tasks from showing that error whenever an agent edits the ticket values.

I'll add the fix below and mark that as the answer, just in case anyone else runs into the same problem in the future.

Kind Regards,
Sam

Sam Thornton_vntjui

The answer that helped me with this issue:

Create a new sub-task screen (without adding the customer request type to the screen)
Create a new sub-task screen schema and associate that with the new screen
Configure the Configure Issue Type Screen Scheme for sub-tasks, by adding the new screen schema to the sub-task issue type.

Sub-tasks are now editable without an error.

shua_v9tk1w

I was unable to edit the "summary" property of the subtask until I added the field to the screen. Thanks!

Welcome!

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

Quick Links

Find more posts tagged with

server

data-center

sub-task

jira-service-management

jira-service-management-server