Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Combining stories

Hi folks,

I am new to Agile and I have a question about merging stories together.

I have currently 2 user stories: one for the selection of an object, one for the rotation of an object. 

- as a user I want to select an object so that I can have interactions with it.

- as a user I want to rotate an object so that I can view it from different angles.

 When I create 2 seperate branches and finish each of the story. At the end I have two independent stories but they have to work together. I may only rotate the object whenever I select the object. How can I achieve this if there are two seperate branches?

Thanks and hope you have a nice day.

1 answer

0 votes
Deleted user Mar 26, 2020

@Hak : Taking a step back and looking at the why's of creating 2 stories, this is how I can put it.

Generally multiple smaller stories/ tasks are created so that when people can PULL them when they are available.

(this would still be applicable in your case of viewing object and rotating object)

Though there will be overhead of branch maintenance while merging the Pull requests, this helps in dividing the things into small chunks and working through them. When it comes to testing, first action for a user would be, to select an object and then play with it, either rotation or moving or anything else that would be needed and accordingly bugs will be raised against them. In some cases, bugs had to be raised at a higher level when there is tight coupling within the stories, that's where another hierarchy of Epics are provided. 

Hope this helps.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Agile

Join us LIVE: Atlassian & Experts Talk Research & Insights @ Scale

Hello all! What have you learned from your customers lately? Our live-streamed series continues by exploring CX, UX, and the power of research & insights at scale with Leisa Reichelt, Head of R...

236 views 3 6
Read article

Community Events

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

Events near you