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!


How to raise work across other Jira teams

Hi. We've around 12 teams in our Jira instance, each defined as a 'Project' and reflecting a technology area (e.g. middleware, infrastructure, databases, portals etc). Often a team will receive a request which needs another teams' involvement to deliver the overall capability (we refer to this as a primary team raising a request on a secondary team(s)) - for example, one requirement might need front-end, middleware and back-end involvement (3 teams). Our current approach is that we have the primary team raise an epic directly on the secondary teams' backlog. However, this means that everyone needs write access to all teams' backlogs - which is leading to out-of-control backlogs which the BA/PO have no control over (they're getting full of noise / badly defined requirements etc).

To counter this, we're considering hardening the entry to the backlogs by making the BA/PO the gatekeepers for their own backlogs, and have all requests come indirectly via them for consideration. Given we're still largely remote, we could rely on email or Teams calls etc to handle this communication, or we could do something in Jira to cover this communication; a bit like a work request 'exchange' - in which a team raises a new issue (we're thinking of using type 'Service Request') citing the source (Team A) and destination team (Team B) plus details of the work required. All receiving teams would get a board filtered on work destined for them. So Team B would then review those inbound requests and add to their backlog themselves accordingly as they see fit, and transition the request to 'Done' as feedback to Team A that it's been actioned. I've configured this and it works fine, but it's another board for teams to manage and I'm wondering if there's a simpler alternative.

Does anyone have any comments for/against this approach - or are there any other suggestions for how we might do this? I guess an obvious answer is to operate in full-stack teams thereby avoiding this need altogether - but that's a huge upheaval which I'm trying to avoid for now.



Log in or Sign up to comment