Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Field Configuration of Sub-Task in Jira Service Management

Matthias Lochmann
Contributor
October 5, 2022

Hi together,

I have prepared a new JSM Project, for that i had defined several Custom Fields. Additional, i need the Sub-Task in cases of escalations. My Problem is, that i can't configure this Fields:
image.png

The Message tells to me, that i need a "Request Type". Ok, i had tried to create a New Request Type for Sub-Task, but that was not possible, i can't choose Sub-Task Issues for creating a new Request Type:

image.png

Ok, wrong path...

So i have tried to remove the fields in the field configuration of the project. But yes, when i remove a field, it appears also not anymore on the other Issue Type, where i need i definitely:

image.png

Ok, also the wrong path... i asume, that i need a different Field Configuration for the Sub-Task, so i have created a new one:

image.png

But, i can't assigne it to Sub-Task ussed in my JSM Project!...

In the end, I have to say that I have no idea how to configure a sub-task for my JSM project separately.... hope someone can help me.... 

 

Thank you & Best Regards

Matthias

 

2 answers

3 votes
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 5, 2022

You've nearly got it.  The step you need next is to go to the "field configuration scheme" for the project and edit that.

It will show you a list of issue types, mapped to various field configurations (quite probably though, as I'd guess you have not edited this yet, it'll probably just say "default: TES"). 

You should add all your sub-task types into this list, mapped to "Sub Task SSC.

Matthias Lochmann
Contributor
October 5, 2022

Thank you @Nic Brough -Adaptavist- i will try it! 

0 votes
Jack Brickey
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
October 5, 2022

Hi @Matthias Lochmann ,

yes indeed a subtask cannot be associated with a request type. Request types are only associated to a 'parent level' issue type. This makes sense given that you cannot create a subtask without first creating its parent. With that said you certainly can have subtask as an issue type in your JSM project. To do so simply go to project settings and then issue types. And the screen you can add additional issue types and should be able to add the subtask. What's the subtask issue type has been added then you should be able to create a subtask while viewing an issue in your project.

Matthias Lochmann
Contributor
October 5, 2022

Hi @Jack Brickey  Thank you! Yes, that is true, it makes sense, for the sub-task, you need a parent task...

It is allready possible to create a sub- task, but on that sub-task, i see all the created custom Fields per default. And that is my problem, i need only a absoultely basic sub-task with two custom fields. But i don't know, how i can configure the sub-task concerning fields in my JSM Project.

Jack Brickey
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
October 5, 2022

Indeed and Nic's answer is the path to take.

Like Jackysusu likes this
Angeline Ygrubay
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 12, 2024

@Matthias Lochmann were you able to make it work? I'd really appreciate if you can share what you did. I'm having the same issue now. 

Creating the subtask's own Field Configuration and editing the issues field config schemes didn't solve my issue.

Appreciate your help! Thanks!

 

 

---

Update: Just needed to 

1. Create a screen for the subtask

2. Create a screen scheme for the subtask

3. Associate the screen scheme to the issue type screen scheme.

This solved the problem.

Like Jack Brickey likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events