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
Our Infrastructure team provides development services to all teams + they have their day-2-day operational work. What would be the best way to manage the different requests coming from all teams?
We have Infrastructure project in jira, which is not 'Product' oriented and used for on-going day-2-day operational work.
Our other JIRA projects are setup to be 'Product' oriented.
When product team member needs Infra services he either opens an issue in the existing Infrastructure project (and then links it to another duplicated issue on his project) OR opens an issue in his project, labels 'Infra' and assigns to Infra team member.
The disadvantages are:
I would like to know if someone has tried to use the below direction and if it works well:
Any ideas for other best practices will be appreciated!
@Meital I was interested reading your query and the solution that you were thinking of. We are on same boat and looking to implement something for our Infra and DBA team. Can you shed some more ideas on your implementation of Infra board please. Any learnings, lessons learnt etc.
We could really benefit from your ideas. Thanks much