How to Split Issues in Jira: A Step-By-Step Guide

preview_player
Показать описание
In this #atlassian #jira video, we will be looking into how to #split issues. Splitting issues is a handy feature available to you in your Jira backlog. You can right click on any issue that is visible in your backlog and then you'll see the option to split your Jira issue. When you decide to split your Jira issue, you'll see the original issue and then you'll have the option to create a new issue and also estimate that new issue. It is at this moment that you can change the title of both issues and also provide, updated, more accurate estimates for your story points. If you need more than 2 issues, you can also add more issues and split the original issue into multiple parts.

If you like this video, please make sure to give it a thumbs up. If you haven't already, please consider subscribing. If you have any questions about anything discussed so far, please feel free to make sure you leave your question in the comments section.

Jira Merch:

Link to my other Atlassian Jira videos

Link to my Atlassian Live Streams:

Link to Atlassian's Jira products:

Link to my Fiverr profile:

Link to my Upwork profile:

Link to my personal website
Рекомендации по теме
Комментарии
Автор

Thank you...subscribing! This was clean and simple to follow as a novice Jira User.

ipsqgyx
Автор

How about subtaks ? why they are not splitting to future sprints as you split the story

FinancialThings
Автор

Thanks for the video! Question- how does splitting the story help if there are still subtasks either in 'to do' or 'in progress'? I know you said it was a topic for another day- but wondering if splitting can get around this issue. Thanks!

jasminefrancis
Автор

is the comments and all the content in the entire story carried over to the new split story ?
Are the bugs and subtasks carried over ?

ranjinimj
Автор

the thing with this, blame Jira, is that subtasks are not "cloned" in the splitted stories

santiagocastrolacroze
Автор

Please could you make a video on burn down charys with jira

mahmoudmahmoud
Автор

i dont like this approach. i think you can take some credit without having the board "lie" for you. what about capacity. did this team plan for a 100pct? maybe they should include a little buffer to mitigate this instead. if you're working software, then 80 pct is still "not done"...

then working on slicing stories in planning is another thing, and perhaps something id focus more on.

jeppesndberg