Note: You will not be able to convert an issue to a sub-task if the issue has sub-tasks of its own. You first need to convert the issue's sub-tasks to standalone issues; you can then convert them to sub-tasks of another issue if you wish. Sub-tasks cannot be moved directly from one issue to another — you will need to convert them to standard 2 Answers. Sorted by: 52. You can do this through the More Actions dropdown: On the Story Page, select the "More Actions" dropdown. then choose the "Move" option. On the following dialog you'll be able to change the issue type to an epic. Share. Using this method, all your new items would come into the backlog and once triaged/groomed they could be moved into the "holding sprint" and prioritized. Think of it as an additional backlog. You could still leave the backlog issues unassigned and only add an assignee when moving them into the "holding sprint". pjd. Hi all, just wondering how I can trigger in the JIRA project automation: "Convert Sub-task to Issue". in the way, that a Sub-task is converted to a. Task or a Stroy. and if so, to keep the current sprint value. Though about Field changes. But how to create a rule with. Type was "Sub-Task" and is now "Task" OR "Story". Do you mean that you want to build a second-level issue type like sub-task？. System administrators can add this issue type. After completing the above configuration, you need to modify the issue type, screen, field, workflow scheme synchronously. Egidijus Č Oct 28, 2019. Move an issue from JIRA Service Desk to JIRA Software. We've been big users of Jira Software for a long time now and are starting to look at the Service Desk application, however I have found one blocker in our testing. Right now, our user access to Jira is open for anonymous users, but if you want to contribute to an issue you need a login. bnIZy. Using this method, all your new items would come into the backlog and once triaged/groomed they could be moved into the "holding sprint" and prioritized. Think of it as an additional backlog. You could still leave the backlog issues unassigned and only add an assignee when moving them into the "holding sprint". pjd. We made a choice by adding sub-bugs as sub-tasks for an "external dependency" reason: We moved recently from TFS to Jira and we still automatically generating tasks and branches in TFS for each task created in Jira and not for sub-tasks (our code and build system is still being managed in TFS for now and for sometime ahead). Each issue you convert to a subtask must have one issue designated as its parent. It cannot have multiple parents. And the parent and subtask issues must be in the same project. During the Bulk Change operation you can only enter an explicit issue key there (i.e. ABC-123), and it can be only one issue key. That issue will become the parent for Thanks. The option to convert the item to sub-defect by clicking on the work item icon does not give me Sub-defect as an available option for selection. It seems to be the most intuitive option. But I could do it by clicking on the three dots on the right upper corner of the defect, select Convert to Sub-Task option, and then change it to Sub Best practice #4: use Outlook alerts to your advantage. The last tip is for situations like when you immediately want to be alerted for certain Jira Software events. When using Outlook rules, you can use the action Display a Message in the alert window. This will show a dialog in Outlook, which you’ll need to confirm. Open your Work page, click on Settings, and click on "Issues". In Issue Types, click on "Add issue type". Enter the name and description and click on "Add". In your project, click on "Create". Click on "Issue type" and choose "Defect". Add your summary, scroll down, add your "Description" and click on "Create".

jira convert task to bug