How to Create new workflow for Subtask in Change request

[Sreenadh]

Hi,

I want to Create New workflow for subtask in change request workflow.

Can some one will help me out is it possible in JSM?

Thanks,

[Vedant Kulkarni_Trundl · Accepted solution]

@Sreenadh Creating a new workflow for subtasks is possible

Do want to deviate a new flow from the particular status of Change Workflow and create a completely new Subtask workflow? Can you elaborate on your end goal?

[Sreenadh]

Hi @Vedant Kulkarni_Trundl 

Sure, Here it is.

Once i create a Change request i see that there is a option to create a Subtask as well.

which you can find it in the below screenshots.

whenever i create sub task i can see Summary, Description, Test plan only. instead of i want to create more fields which are Category, Change reason, pending reason, Change request approver, production deployment approver, Change start date, change end date..... etc.

and also

I want to implement workflow for Change request sub task.

Change Request workflow is different

Change request Sub task workflow is different.

Hope you are able understood the requirement

Thanks,

[Vedant Kulkarni_Trundl]

@Sreenadh 

there is a sequence of configuration steps that you will have to follow.

1. create the custom fields Category, Change reason .... ref: Create a custom field | Atlassian Support
2. once you create them associated with screens ref: Add a custom field to a screen | Atlassian Support
3. confirm the screens are associated with your project ref: Manage screen schemes | Atlassian Support, Manage issue type screens | Atlassian Support
4. to implement a new workflow, you have to create a workflow first ref: What are Jira workflows? | Jira Software Cloud | Atlassian Support
5. Associate the newly created workflow with the project's scheme ref: Configure workflow schemes | Atlassian Support

[Hamza Chundrigar]

Hi @Sreenadh 

You are able to create and associate a different workflow to whichever issue type you have in your project. In your case, yes — you can have a different workflow for "subtasks".

First, you will need to make sure you create the workflow that you want this subtask to have. You need to be a Jira administrator to create and edit workflows.

This article shows you how you can create a new workflow

Create a new workflow

If there isn't an existing workflow to meet your needs, you can create a new one then use it with your project.

1. Go to Settings () > Issues

2. Choose Workflows and click Add workflow.

3. Do both of the following until you've built your workflow:

   • Click Add status to add a new step to the workflow (you can add existing statuses or create new ones)

   • Click Add transition or drag from a node on one status to another to add a transition

4. Click Publish Draft.

Select the new workflow to use with your project:

1. Choose Projects and select a starred or recent project, or choose View all projects and select a project.

2. From your project's sidebar, select Project settings > Workflows.

3. Click Add workflow and choose Add Existing

4. Select your new workflow and click Next

5. Choose the issue types that'll use this workflow and click Finish

6. Click Publish and click Associate to migrate any existing issues to the new statuses in your workflow

Managing Issue Screens

Since you need to display different/additional fields on your issue type 'Subtasks' you can choose to create a custom screen that allows you to controls which fields you want to display for subtasks issue type. See here how you can configure screens as well as the tabs and fields within them.

you will also need to create a screen scheme and then associate this screen scheme with the sub-task issue type in your project's issue type screen scheme.

Tip: An issue type screen scheme associates a screen scheme (which defines mappings between screens and issue operations) with issue types. Hence, an issue type screen scheme allows you to specify different screens for different issues types when used for the same issue operation (e.g. 'Create Issue') in a given Jira project. 

Regards,
Hamza