Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Flipping sprints using the Split function

My team has been using the Split function when their tasks end up needing more than 1 sprint to complete.  They complain (like many others) that there are fields and attachments that are not copied over to the new split task.  

While sitting in with another team during their sprint planning I saw person split a task but put the new task in the current sprint and send the old task forward to the new sprint.  While Jira certainly allows this use of the Split function it just seems wrong to me, even though I could not come up with a hard reason why not.  

Does anyone have experience using Split in this manner?  It just seems wrong but I am trying to be open-minded. Thanks. 

ps.  When I look at the fields that don't make it to the new task, it seems very problematic since it will be missing important fields such as Status, Resolution, Time Spent, etc. 



Log in or Sign up to comment