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

Work spread over multiple sprints

I have setup following hierarchy in JIRA, user-story (issue) > BE subtask & FE subtask. Since we have a small team FE tasks are completed and queued up while BE tasks follow later. This is leading to piling up of user stories on sprint board. What would be the best approach to keep track of the issues and keep the sprint board clean?


FYI - reason to use the above hierarchy is to keep track of completion of each user story.


Looking forward to hear your suggestions.




1 answer

0 votes

Welcome to the Atlassian Community!

In Scrum, you should be sizing your stories such that they can be executed (ideally many of them) within a single sprint.  "Work spread over multiple sprints" should be a rare exception.

Your best approach is to refine your stories better, breaking them up into more manageable stories.  Or you could increase the length of your sprints so you can fit them in.

Suggest an answer

Log in or Sign up to answer
Site Admin

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