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
This discussion question centers more around Jira, but could apply to other Atlassian tools as well. With my job as a Jira Administrator, I get a lot of customization request. Can we add this field, have this status in our workflow, change up our screens? Some times things are pretty simple, but sometimes the requests are very specific and granular.
We'd like this Custom field to be drop down instead of check boxes, or lets reword the name of this Custom field from Origin to Point of Origin. We want very specific users to be able to do very specific things etc. Making it difficult to keep things shareable, and even just manageable in a large environment!
How do you balance between what customers want (and by customers, this could be teammates, other users in your office, or a client) and what is really best practices in Jira? Are there some good tips for assisting with determining the actual needs of folks making the requests? How do you steer them to options that work best for the global environment vs the one time specific use?