Merging user stories

During product backlog grooming we often encounter stories that are quite small and could be easily combined with other stories. How does one go about merging user stories in Jira? It doesn't look to me like there is a special functionality for it (link type, history). Any good practices?

Also, correspondingly, how do you best split user stories into smaller ones, preserving traceability?

3 answers

What if you regroup these small stories under the same Epic? Since an Epic is basically a large story meant to be broken down in smaller stories, if you have small stories to begin with, regrouping them under an Epic seems to make sense, with the added benefit of having all these small stories easily accessible from within the Epic, or by filtering from the Backlog view.

Thank you Nicolas, but your answer doesn't really solve my problem.

My case: I already have the stories grouped under a certain epic. During the grooming we realised that one of the stories is not independent, but rather should be a part of another story as one of the acceptance criteria.

US1: As an administrator I want to see a list of all the user accounts I created 
US2: As an administrator I want to see when a user account was created
These and many other are part of an epic: Manage user accounts

What I did now, was to link US2 as related to US1 and close US2 as duplicate, but this doesn't really show what I was trying to achieve: merge two user stories into one.

During product backlog grooming, one doesn't only split epics into smaller user stories, but sometimes merges stories. I miss a proper workflow for that in JIRA Agile.

I see. But how could there be an automated way to do that? How could JIRA "know" how excatly these stories should be merged? If simply appending the descriptions and adding the time estimates was enough, a script could do that. If you require something more complex and flexible, that's a good plugin idea, as I haven't seen anything like that on the marketplace. In the mean time, you could create a new issue link called "Merge", with the links being "Merges / Merged into". That at least would be clearer than a duplicate.

Creating a new issue link type is a good idea for starters. Thank you for that! I'd like to accept your answer but I can't cause it's here as a comment to mine answer (which should have been a comment, ouch :)). Do you want to re-post it as an answer?

We released a Jira cloud app called Merge Agent for Jira that could solve your problem.

With our app you can easily merge the description, comments and other content of two tickets or several tickets with just a few clicks. 

Feel free to get in touch with us if you have any feedback on Merge Agent for Jira.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Feb 26, 2019 in Jira Software

How to prevent the propagation of unused project schemes, workflows & screens in Jira software

Atlassian ranks project attributes as the third most important factor impacting performance in the category of data. It’s not surprising, since project attributes are precisely the rules used to ma...

633 views 0 7
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you