This end up in tough to manage situation. But if somehow you end up creating duplicate issue you have two options, Link duplicate issue to existing issue as duplicate. Any person who have access to edit issue link permission in Jira can do this. When you close main issue, you can also close duplicate issue. You can also write some automation on
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}}
You can use Bulk Move. Open subtask, there is "Move" option in three dots submenu. Set destination project to same as your source. Change destination type to "Story". Same - I currently want to convert some sub-tasks that I realized should be their own tasks. This is a pretty broken aspect of next-gen projects.
Navigate to the issue you would like to convert. Select More > Convert to Sub-Task. In the Step 1. Select Parent Issue and Sub-Task Type screen, type or select the appropriate parent issue type and the new issue type (i.e. a sub-task issue type). Click Next. If the issue's current status is not an allowed status for the new issue type, the Step 2.
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.
. 246 154 249 44 269 345 98 109
jira convert task to bug
