Regards. If you open the story, click on the 3 dots in the top right corner, then click on Move. You are than able to change either the Project or Issue Type. Click the dropdown for the Issue Type and choose Subtask, then a box opens to choose which parent to move it under.
Step 1: Create a sprint. Go to the Backlog of your Scrum project. Click the Create Sprint button at the top of the backlog. Note that you can create more than one sprint, if you want to plan work several weeks in advance.
Kanban and Scrum boards are just a visualisation of your filtered work - there is no way to convert a Scrum board into a Kanban board, but you can create a new board and visualise it. This is how to do this: Go to Boards > Create Board > Create a Kanban board. Select to create the board from an existing saved filter and click Next.
But I noticed the following: When you have a Story ticket (which appears in the sprint board and backlog views) and convert it into an Epic (using the "Move" function), then magically the ticket still appears in the sprint board, now as an Epic. Weird thing is, that when you search for it on the Backlog view, it does appear as an Epic in the
4 answers. Issues, by definition, belong in a single project. If you have pieces of work that span different projects, you should look at your project structure (it's not matching how you work), or split the issue into pieces, one for each project that needs to look at it. It's not quite a case of duplicating it, it's a case of splitting it
. 246 29 349 123 473 88 296 486
jira convert ticket to epic
