Providing more visibility of subtask estimation at the parent issue, on the backlog, and in reporting. Allowing for subtasks to be rank ed within its parent issue; Adding additional information in the swimlane headers when grouping by subtasks are enabled. Making it possible to convert a subtask to another issue, for example a story or task

Step 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.

1 accepted. you just need to transition the issue back to the status that is mapped to Backlog. Likely this is "To Do". If you are unable to do that then it would likely mean that there is not a transition from the status you are in back to To Do.
1 accepted. Go to the board settings -> columns and have a look what statuses are mapped to the backlog. After you do it, make sure that you have a transition from the TODO column status to the status in the Backlog column. You can see transitions in the project workflow scheme defined for your project.
I am just not positive how to actually convert a issue to a subtask using scriptrunner for jira cloud. // link issue block of code. // Specify the source issue. final sourceIssueKey = issue.fields.key. // Specify the target issue. final targetIssueKey = 'queuedissueparent'. // Specify the link type to use. final linkType = "Relates". In Next Gen, use Jira Automation to create a new rule. Trigger: Issue Transitioned (I used from In Progress to In Review) Condition: Advanced Compare Condition. First Value: { {worklog.comment}} Condition equals. Second value empty. Action: Send email. You can also do this with comments using same Condition and first value { {comment}} nlezX. 356 55 382 79 35 489 284 173 453

jira convert task to bug