How to configure hte Issue view for subtaks

[Simon Sahli]

Hello community,

We are currently moving from Jira Server to Jira Cloud and I want to configure the "Issue view" for one JSM project.

Now I am able to configure with the "Issue view" for the request types, which fields I want to have displayed where, which works well.
However I would like to do the same for the subtask (work order issue type).
The subtask issue type is obviously no request type though and thus not visible in the request type menu.

So how can I access the issue view for a subtask issue type in order to configure which fields are shown where?

Thanks in advance!

Cheers,
Simon

[Simon Sahli]

I put some more time into configuring the fields on a screen for a subtasks and I must say I either do not understand it yet completely, or it the functionality is pretty limited (with the new issue view at least) for subtasks.

For example, how can I get rid of the "Request type" field on the subtask view?
It is not possible to have a request type on the subtask, so I do not want to have the request type visible all the time under the "Detail" section.
I thought if I remove it from the "View" and "Edit" screen for the subtask issue type it would disappear from the subtask view screen, but it does not.
Am I missing something or is this actually not possible?

[Nic Brough -Adaptavist-]

Service Management project's main purpose is to gather requests from people, not break down activity into smaller parts, so the sub-task functionality, in my opinion, has not really been reviewed and changed to make it work better for JSM projects.

Yes, you're right in that there should not really be a request in front of a subtask, because the customer will never see it, nor does it add anything.  As sub-tasks are a part of their parent issue, they should really be referencing the request that is paired with the parent issue (if there is one)

But Atlassian have not coded for that.  The best you can do is remove the "field" from the view, edit, and create screens.

[Simon Sahli]

Hi @Nic Brough -Adaptavist-

thanks for the explanation.
However, I have tried to remove the "Request Type" field from the View/Edit screens for the subtask, but JSM still shows them.

Following you see a subtask and the "Find your field" that says it should not be present on the issue view for this subtask issue:

This sounds looks a "bug". Do you agree?

Best,
Simon

[Nic Brough -Adaptavist-]

Not really, JSM  project's main purpose is to gather requests from people, not break down activity into smaller parts, so the sub-task functionality is not great.  

The simple answer is "stop trying to use sub-tasks in places where they are of little or no use"

[Nic Brough -Adaptavist-]

Hi Simon,

JSM does not really have a big use-case for sub-tasks.  This is mostly because they are completely irrelevant to the customer raising the requests, and most Agents don't need them - they will tend to create issues in other development projects to cover bits of requests that need someone else to look at.

You can create and use sub-tasks in JSM projects, and they work the same way as sub-tasks in JSW and JSM projects, but the customer will never see them. 

If your JSM project is company-managed, look to the "issue type screen scheme" - you need one that says "for issue type X use these screens, and for Y, use a different set" (probably with X being most or all of your base level issue types like Stories, and Y being most or all of your sub-task types)

If your project is team-managed, you have to go into each issue type to configure it.