Converting issues to another issue type not working, option has changed to 'convert to sub task'. Satyendra Luckwani Jul 22, 2019. Initially we used to get an option of just 'Convert', wherein we could change the issue type to any of the standard issue types. Now this option is not there, and is changed to 'Convert to Sub Task' only. You should see this "Move" button on issue view screen. In order to move an issue, you need to have a "Move Issues" permission. Please check this from project -> settings -> permissions. Thank you it helps. @Tansu Akdeniz : I tried this but there is no way to move Task from one project to another. We can move Issues by following this but not Task. 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 Auto Clone a task as a subtask in another project when you link to the Parent in the other project. Karen Kelly Feb 15, 2023. I have a project where we import trades from a spreadsheet every day as standard Task tickets in ARBBLOTTER. Instead of going into our POSKEEPER project and creating BUY and SELL subtasks linking to the relevant tickets I recently set up a Jira project for tech infrastructure program with a 20 year old waterfall culture. My supervisor made a random ask to add "spike" issue type to the Jira project. I believe the need is for providing research tasks to one of the four teams using the project. Create a problem issue. A problem issue is created to record information regarding a problem that has occurred so it can be investigated. When correctly managed, problem issues prompt agents to detail known errors and workarounds in your knowledge base to: Select Create. Select Problem as the issue type. Enter relevant information. You can bulk move both standard issues and sub-tasks to another project and issue type, as well as convert a sub-task to an issue and vice versa. To learn more about issue types, see Issue fields and statuses. You can also select both a sub-task and its parent to bulk move. Here's what I'm doing to try to export an issue to a document: 1. Open an issue, any issue. 2. Export to Word (see screenshot below) 3. Open the document in Wordpad, which support MS Word in Windows 10. - Or, upload the doc to Google Drive and double click on it. Expected Result: To get a binary MS Word document with the contents of the issue. Sub-tasks cannot be moved directly from one issue to another — you will need to convert them to standard issues, then to sub-tasks of their new parent issue. Restricting access to an issue When creating (or editing) an issue, you can restrict access to that issue to members of your team who are part of a chosen security level. 3. Task can have sub-tasks, but a task can’t be a sub-task of a task. I’ve been working with Jira for 9 months now and still I can’t stop laughing while reading the above subtitle. An issue on Jira can be a task or a sub-task of a task. However, existing task can’t be a sub-task of a task. You’d need to “convert” existing task to o12Lm.