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 standardCreating Different SubTask Issue Types in a Team-Managed Project. Sarah Sheffield Nov 05, 2021. My team uses a team-managed project as we like the flexibility it gives us to adjust as we go and improve our processes. We have several issue types that we have created and we have enabled subtasks. Now we would like to create different types ofStep 1: Identify technical debt. At first glance, many people assume technical debt = bugs. Sure, bugs are a certain kind of technical debt, but technical debt is more than just bugs. Technical debt is outstanding work promised but not delivered to the customer, defects in the code, or work items that hurt agility. 5 days ago · 2 accepted. In order to export Jira issues in form of a CSV/ Excel file, just search for the relevant issues using filters/ JQL and then use the "Export" button to get access to all the export options. Next select the option "Export Excel CSV" to export the issues. Check below screenshot for more details.
2 answers. It is permission based, so it might be down to a role. Check what the permission scheme for the project says about who has the permission to "move" and "edit" issues. You can perform a simple edit on the issue type IF the source and target issue types are configured identically. If they are not, then you have to use the "move" option