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!


Sub tasks, do they need Team assigning?

I think I know the answer to this but I just want to confirm.

We have a project within Jira cloud that is used by multiple teams, each having their own board. Each board filter has 'team = ABC', 'team = DEF' and so on. Currently the teams only use stories, tasks etc., but now want to use subtasks as well. My question is, because the board filter works on team name, does each subtask also need to have the team name populated? I know subtasks are part of the story and therefore the same team, but because the board filter is looking for the team name, unless it is set for every subtask, they don't appear on the board.

I'm trying to achieve this without any addons which I suspect will be the resolution. My alternative option if this is not possible would be to create automation rules when a subtask is created to set the team to be the same as its parent issue, and when a parent issue is updated then all subtasks are checked and updated (for when a story moves across to a different team).

Any help / responses would be appreciated.

1 answer

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

Hi @Paul Smith ,

I am sure you probably have a good reason to have multiple teams working on the same project. Just as a teaser, if you split all the work by team anyway (which you are doing by assigning every task/story to a team), have you considered the option to have teams work in their own projects? 

Apart from that and assuming that there's very good reasons behind your current setup, I think automation is a perfect fit for your use case. Just making sure that you let your team assignment roll down automatically from the parent issue to your sub-tasks should ensure all work remains consistently visible to the teams. I don't see any reason for marketplace apps here.

Hope this helps!

Thanks @Walter Buggenhout , I thought automation would be the way to go.

Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events