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 just started a new role, at a new company, and JIRA is used differently across every team. There are no enterprise standards for how the tool should be used, in terms of agile development. In my past roles, I've always used JIRA as a tool to manage agile development for just my team. At my new company, there are project managers who require developers across several teams to use one JIRA project for their tasks.
I would prefer to have my team track tasks within our own JIRA project, versus one big project that several different teams track in. I want to develop my own team's velocity and have visibility to task status without having to use a custom filter to pull everything together from several projects outside of my team's project.
Has anyone run into this predicament before? I don't want to create redundancy and I don't want to interrupt a PM's existing process. At the same time, I don't believe a PM needs to track the detailed tasks my team is working on within their project.