sometimes issues are created as sub-tasks when they should not be. sometimes a sub-task outlasts the issue for which it is a sub-task and it needs to become a task of its own; Currently the workaround is to close the issue and open a new issue, but this is not ideal, as the issue ID changes rendering any links to the issue dangling.
Answer accepted. That is still the case. You can't add subtasks to sprints or move them to backlog without moving the parent story. You will have to either convert the subtasks to stories or split the story and move the subtasks to the new story. The stories should then be moved to the backlog.
Bug Tracking: This is suitable for teams focusing on managing and resolving bugs. Task Tracking: For general task management, this template allows teams to track progress on various tasks. Each Jira product comes with its unique project templates catering to specific workflows. For instance: Jira Software: Offers Scrum and Kanban templates 1 answer. I don't think users have access to change the issue type of posted issue. Though, what you can do, is post a comment on it. So whoever from Atlassian picks it up, will definitely be reading through issue as well as comments. Thanks, i have done it there is red icon on top of the posted bug, whereas we can change it. 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 To change an issue’s status with the command palette: Make sure you’re viewing an issue either in the side bar or in full screen. Open the command palette. If you’re a Mac user, press command + K to open the command palette. If you’re a windows user, press Ctrl + K to open the command palette. Search for the command Change status. I'm using Jira Server 8.0.3. I created a new issue type and a workflow associated with it. Before this new issue type we used to control the work with stories. I'd like to convert some stories to this new issue type but when I try to edit a story and change its issue type, it only allows me to change it to a Bug, Task or Epic.

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.

Indeed, the new issue view of JIRA does not have the convert sub-task to issue feature, so we created a bug to fix it: - New Full View Issue Experience eliminates convert subtask to issue feature. Please, watch and vote the feature request to receive any updates about it and also increase its priority. Let us know if you have any other questions. TAmadeq.
  • yq4hz361mr.pages.dev/341
  • yq4hz361mr.pages.dev/727
  • yq4hz361mr.pages.dev/233
  • yq4hz361mr.pages.dev/447
  • yq4hz361mr.pages.dev/710
  • yq4hz361mr.pages.dev/488
  • yq4hz361mr.pages.dev/478
  • yq4hz361mr.pages.dev/782
  • yq4hz361mr.pages.dev/264
  • yq4hz361mr.pages.dev/15
  • yq4hz361mr.pages.dev/688
  • yq4hz361mr.pages.dev/355
  • yq4hz361mr.pages.dev/977
  • yq4hz361mr.pages.dev/174
  • yq4hz361mr.pages.dev/127

    • jira convert task to bug