You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I would like to have a better overview of which epic to which team is assigned, and for this to be visible in each Team’s backlog.
In my previous company, we had a field called “Contributors “, where we select each team involved in the delivery of the different features. Due to this field, we had 1 epic that held all teams and their tasks. But I am not sure how this filed was created and configured as we had a JIRA Admin that implements all the requests, and I was working with only 1 of the teams where we have a separate board with the team tasks.
Can someone help me with this as I will work with a lot of teams and I need this?
What problem are you trying to solve by doing this?
For example, to provide earlier visibility of scheduling / participation by different teams, to help teams see with whom they will collaborate, etc. Knowing that may help the community to offer suggestions to better help.
In the meantime, have you looked at the Jira Product Discovery tool and features, as that can help with the flow from ideation-to-delivery, scheduling, etc. I have seen this used with a Teams field for both early coordination and scrum-of-scrums converations. Please look here to learn more about that tool: https://www.atlassian.com/software/jira/product-discovery
I found what I need but we need to wait until this feature is live.
These two tickets represent the business’s need to have multiple teams assigned to a single epic so that we can view the epic on different team boards:
- Jira Server https://jira.atlassian.com/browse/JSWSERVER-25177
- Jira Cloud https://jira.atlassian.com/browse/JSWCLOUD-20347
Thank you for clarifying the scenario.
Next thing, I am just another Jira user, and not an employee of Atlassian. With that disclaimer out of the way...
Please note those suggestions were created in 2015. I do not believe they will ever be implemented. The idea of the Assignee field seems to be accountability: there is one person (Jira user) assigned to an issue. Even when there is team collaboration, there is a single point of contact for the work...according to the Jira implementation.
Jira users sometimes work-around this limitation by adding custom fields like Additional Assignees (multi-select user field), Teams (multi-select field), etc. When those are done the additional criteria can be added to different teams' board filters so the issues are visible.
Unfortunately, I believe there are multiple "Team" fields in Jira for the various products, and some are single-select. That leads people to add a new custom field for what you asked.