Regards. If you open the story, click on the 3 dots in the top right corner, then click on Move. You are than able to change either the Project or Issue Type. Click the dropdown for the Issue Type and choose Subtask, then a box opens to choose which parent to move it under. Once you’ve logged in to your Jira account, navigate to the project in question and click the global Create button in the top toolbar. In the resulting window ( Figure A ), make sure to select 1. If you already have a new workflow and you want to apply on your existing project: 2. If you doesn't want to affect the current project then you need to make a copy of your existing workflow scheme or create new one and associate workflow with issue types and then use it. Go To Admin button (gear icon) > Issues > Workflow schemes , it will

I've setup the following hierachy for one of our projects: 1 level: Initiative -> linked to Jira issue type INITIATIVE. 2 level: Epic -> linked to Jira issue type EPIC. 3 level: Stoy -> linked to Jira issue type STORY. 4 level: Sub-task -> linked to Jira issue type SUB-TASK.

1 answer. We use both in our software projects. Epics are issue types, used as high level deliverables that are broken into smaller stories. The epic follows a workflow and is closed once it is completed (released). You can estimate, plan and track your progress on a deliverable using the epics. (The workflow can also be automated, based on the
Answer accepted. As the automation for sub-task is triggered when a Task is created, it considers the Task as the issue. Hence, when we say, { {issue.parent.epic.summary}}, the automation is unable to understand as the Task has Epic as the parent. Update the automation with ' { {issue.epic.summary}} : { {issue.summary}} : Task-1'.
daA97i. 259 430 298 380 299 164 394 196 201

jira convert ticket to epic