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

how do I create 3 separate backlogs for a project with 3 workstreams

ade ajiboye
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 23, 2023

I have a poject with 3 workstreams and would like to create a seprate backlog for each workstream to avoid any mix up so when a team member selects their board it only displays work relevant to the team. I would also like this sort of display when we view Epics from Roadmap view. Thanks

1 answer

1 vote
Walter Buggenhout _ACA IT_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 23, 2023

Hi @ade ajiboye and welcome to the Community!

Either create 3 separate Jira projects for each workstream (a Jira project and a project in the real world are different things). That creates a clear separation of the work(streams) right from the start.

Or, if you have good reasons to keep all the work in one single Jira project, make sure you can clearly identify the workstream each issue belongs to. You can do so using components or with a custom field you define yourself, having the different workstreams as values. Then, create separate boards on top of your project, where each board is based on a filter that contains the issues from a single workstream. Use company managed projects for this scenario, so you can create multiple boards for your project.

You could find different ways to identify your workstreams (using labels, teams, ...), whatever suits your way of working best. But the above are the two most fundamental ways of approaching this challenge. When choosing either one, ask yourself what the main drivers are to keep the workstreams separated. And also: what they have in common. Things like common components or fix versions (releases) may help you decide to use one or multiple projects.

Hope this helps!

Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events