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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
As our JIRA database grows, managing project lead roles when longtime managers leave the company is not ideal. ie. Assigning new Project Leads when someone's account is deactivated. Also, reassigning Project Leads on EVERY archived project seems a bit silly.
If I created a placeholder account within JIRA that would be the Project Lead for these projects and set the actual Project Manager as an Admin within the project, I believe the only difference would be that the project manager would not be assigned new issues without components specified, correct?
I'm kind of baffled as to why Atlassian would say the way Project Lead role is handled is not a priority.
Yea, that's a good workaround. But we do not user 'Project Lead' much, this will be usually the admin who created the JIRA project and all project managers will be added to the Administrator role