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
It was inevitable. After some time using the brand new, “clean” slate of Jira project configurations, additional adjustments needed to be made. I am not resistant to additional changes. In fact, I inform team members that they should expect changes to the initial configuration to occur in order to adapt to changing business needs - a big selling point for adopting the Jira platform.
Before I even begin to fulfill the incoming request, I hit the brakes and run through a few questions before any configuration. Here are the questions I ask before implementing the configuration:
Note: These thoughts only pertain to configurations that support company-managed projects. Team-managed projects don’t require much involvement from Jira administrators.
Once I run the configuration request through these questions, I’ll implement, validate, and ask the requestor to validate the configuration.
This is my thought process for Jira administration. Yes, I realize that these principles are useful when administering other systems as well! Fellow Jira administrators, what is your thought process and approach to Jira administration on the sites you manage?