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 include small projects into a big one

Hi All,

I have a team assigned to one project it is project implementation, we have a kanban board and a Scrum board, however, we constantly receive requests that could be considered small projects and we need to track the tasks, time etc. How can I include those projects in the big one, without creating a "New project"? 

Thank you!



1 answer

1 accepted

0 votes
Answer accepted
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Aug 16, 2022

There's no way to do this, especially with team-managed projects (they're really not built for sharing data outside the single team that owns each one)

But with a Scrum and Kanban board, assuming they're from company-managed projects, you can do some stuff.

I'm going to imagine you've got a simple case of

  • one company-managed project that they do most of their work in. 
  • one Scrum board  (don't have more than one scrum board for a team, that way lies madness)
  • one or many Kanban boards
  • all based on the same filter of "Project = ABC".  
  • Then there's a pile of other "small" projects, (let's call the first couple DEF and GHI) that you might want to draw some issues from sometimes
  • Including the "small" items in another project can only be done by moving them into the other project.  This loses them from the original project, can easily cause data loss (it's a right pain moving between TMP and CMP) and should never be part of a standard process. 

But with boards, we have some more power.  If you can identify a good way for your users to do this, you can draw the small issues into your Kanban and Scrum boards.

A lot of people do some variant of this.  I use this query because labels are built-in and simple to add, but to avoid slepping mistrackes, many use other fields like a select list for "other team" or "team dependency".


Project = ABC or ( Project in (DEF, GHI) and label = "For-ABC")

Now, if someone adds "For-ABC" to an issue in those two projects, the ABC team will get it on their boards.  (Note - you will need to re-map columns in your boards to include the other projects)

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events