Can we create a Subtask fields in Change Request and need to create separte workflow for subtask

Question

Hi,

Is it possible can we create Subtask fields and workflow under change request both the fields and Workflow is different.

For ex: Once i create Change Request their i can see sub task if i create the sub task under the change request

i want to create a fields for Subtask and workflow also for Subtask.

Thanks,

Nic Brough -Adaptavist- · Answer

You've had this new question answered at https://community.atlassian.com/t5/Jira-Service-Management/How-to-Create-new-workflow-for-Subtask-in-Change-request/qaq-p/2200966

Sreenadh_5t0th7 · Answer

Hi @Nic Brough -Adaptavist-

Thanks for the response.!

But my question is Once i create the change request i can see that "Create sub task"

link

I want to modify the fields of Subtask.

If i create subtask i want to my configured fields.

but i can see only three fields here.

Thanks,

Nic Brough -Adaptavist- · Answer

No, but yes, sort of.  I struggle to write a short plain English explanation, so I'm going to try looking at the components of the question instead.

* Request: an object that a customer creates, representing something they need help with.  A request has an issue behind it, with a 1:1 relationship, but the customer does not see the issue.
* Issue: an object that represents something that needs some attention from a team (in the case of JSM projects, this means the team of Agents tasked with handling the requests/issues)
* Sub-task: a type of issue that is not an issue in its own right, but a fragment or part of a larger issue.

So.  You can't create sub-tasks for a request.  There's no such concept as a sub-request.  But, you can create sub-tasks for issues, so the Agents can split up the issues to help the team process different parts of an issue.  It does not matter that the issue might have been created because someone raised a request, it's up to the Agents to decide if they can make use of sub-tasks.  The customer will never see the sub-tasks because they are issues, not requests.

And the last part of your question - absolutely yes - the main reasons for having sub-tasks is that they can be allocated to different people, have different fields, and follow different workflows