For a mere moment there was a command, "Split," that allowed me to not clone, but split an issue. Now, however, it seems to be gone. I feel like I'm losing my mind, but I did actually find proof:
Does anyone know what the "split" command is (I swear it was "split") and what might have happened to it? Thanks!
I have the impression that - although not immediately visible on your screenshot - you have multiple issues selected. I think so because the bulk change option is showing.
I tried to reproduce this behaviour on a cloud instance and am seeing exactly this. As soon as I select only 1 issue, the split issue option appears in the menu.
Apart from that, a question to you too - how did you manage to get your issue key at the left of your issue cards?
I didn't do anything to put the issue key on the left side. It was always there.
I'm selecting only one issue. If I select more than one, the "Delete" option disapears from the pop up menu, but the other options remain the same.
I'm using Jira Server 7.3.4 not Jira Cloud. I don't know if this makes any difference.
You're not going crazy
This is brand new functionality to actually split an issue in 2.
Screen Shot 2016-12-28 at 14.03.15.png
It is intended to split up a larger story into smaller chunks, which you could add to different sprints. The nice thing about it, is that it copies all relevant information from your original story and then also handles all the logic of setting the correct status etc.
You find this functionality in backlog view by right clicking an issue. On cloud only for the moment or coming soon.
You aren't losing your mind. It depends which browser you are on. On Safari you can never get to the "Split issue" as cursor focus is off just as you try to make this selection.
On Chrome this works, alas you'd imagine splitting would keep all attributes on the story the same. So for instance you have a field called "Team" then it should retain the value, alas it doesn't. Also relative position in the backlog, at least should start adjacent to the story being split, alas it doesn't and you have to go and find that darn split.
In truth "split issue" ideally should land you in an edit mode for the split as one will typically make updates to the story (description, acceptance criteria etc.) and it doesn't.
Really the people who designed this likely only think in terms of 'functionality' vs. "what job is the person/team trying to do at the time?"
I also found that Split is not available for the view of a single issue (surprisingly), so at first I thought it was because the issue was In Progress in a sprint. However it's just that for some reason JIRA decided you can only split an issue from the view of the Backlog ... great feature, much cleaner than cloning, and would suggest it be available when editing an issue.
What is the difference between "split" and "clone"?
Besides, of course, clone you can do from anywhere, and split, in Atlassian's wisdom, is only accessable from the backlog list view. (Someone will come in here explaining why that's by design, why it'd be dumb to split an item not in the backlog, etc.)
Split and Clone serves two different purposes -
Split - Is useful in case there is a leftover task which cannot be completed in the current sprint and has to pass on to either product backlog or next sprint. It allows to split the issue into two (or more) issues, and also provides the facility of splitting the estimates. For example, if a user story which is part of the current sprint has got 4 sub tasks, and the work will be completed only for 3 sub tasks in the current sprint, then this user story can be divided into two - one part can have 3 sub tasks which are completed and other can have the pending 4th task. Their estimates can also be defined accordingly.
Clone - A standard issue can be created for the repetitive work activities and each time instead of creating a new user story from scratch and adding sub tasks manually, it can be cloned from the existing one which eventually saves effort.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events