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?
[Note: So it was my turn for Friday Fun and sadly I was sick thanks to rubbish sinus infection... so apologies to most of Europe and Asia for the delayed post. However, I finally got out of bed for t...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs