Convert Task to EPIC using Jira Automation rule

[Pravin_Gumgaonkar]

Hi Team Greetings of the day,

I am trying to create the Jira Automation rule which can convert my task to New EPIC.

Once the epic is created, I can create the sub task under newly created EPIC. I was trying to do that but unable to get that.

Error:  The fields set during transition aren't available. Fields ignored:

Can you please suggest what's need to be done in that case.

[John Funk]

Hi Pravin,

The issue types much be using the same workflow (sharing) in order to be able to simply update the Issue Type. If the two issue types do not use the same workflow, then you have a to a Move function using the 3 dots menu in the upper right of the issue screen. 

However, you cannot do a Move function using automation - it is only available manually. 

[Bill Sheboy]

Hi @Pravin_Gumgaonkar 

Adding to John's suggestions...

Moving work items (formerly called "issues") from one project or type to another can be challenging due to differences in types, fields, workflows, etc.  This is why Jira has a dedicated UX feature to help: Move.  The move can interact with a person, asking clarifying questions to ensure success.  Automation rules do not have such a "move" action (between projects and types) and cannot pause to ask those clarifying questions.  In my opinion, this is one reason using the Edit Work Item action to change types is a not a good idea, likely leading to errors.

If you can accurately predict any situations to handle for types, fields, workflows, etc., an automation rule could use the Send Web Request action to call the REST API endpoint to move the work item (with the bulk move endpoint), selecting all of the necessary changes to fields, status, etc.

Kind regards,
Bill

[Karan Sachdev]

Hello @Pravin_Gumgaonkar

This error is usually seen when the destination issue type uses a different workflow, and there are no transitions available. If your task and epic use different workflows, this might be expected. I noticed this warning when updating the issue type using automation rule:

You may check this bug for details: https://jira.atlassian.com/browse/JRACLOUD-68207

Thanks!

[Pravin_Gumgaonkar]

Is there any way. I can achieve the below functionality.

• The Jira Task is created.
• Once the task is created, based on Certain filed (i.e. Matching Criteria) I need to convert that task into EPIC.
• Once the EPIC is created, I need to create the 5-6 different subtask.

Can you please guide me how I can achieve that or any reference article, that will help for me.

[Karan Sachdev]

Hey Pravin,

We will need 2 rules for this:

Rule 1: To convert task to epic upon issue creation. Please note that both issue types should have same workflows. If you have different workflows for epic and tasks, then the first status of the task must exist in the Epic's workflow. This is a simple rule:

When: Issue created

If: condition is met

Then: Edit issue: Change issue type to Epic

Rule 2: This will create new child issues under the Epic (Story/Bug/Task etc) when the issue type is updated.

PS. Make sure to check the option at the bottom of the Rule Details page: "Check to allow other rule actions to trigger this rule. Only enable this if you need this rule to execute in response to another rule."

Thanks!