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
Over time, every Jira instance accumulates data, configuration settings and administration decisions that grow old and outdated. A well-defined governance model is required to prevent information entropy from speeding up and killing performance, and sometimes this model is there from the start -- but very often it’s not because Jira has been adopted from the bottom, spreading across departments and teams without real coordination.
That doesn’t mean it’s too late to create the model: it’s should never be too late for killing chaos. It just means the model is harder to build because, rather than starting with an empty canvas, you first need to understand what kind of monster you’re dealing with.
Always start with a diagnosis that tells you how fragmented your Jira instance is. At DEISER, an Atlassian Enterprise Platinum Solution Partner, we have found a way to automate this task with Profields, saving hours of work to our consultants (and our customers) and eliminating errors.
(For full disclosure, Profields is a tool developed by DEISER, my employer.)
Our solution is to create pie charts with the distribution of project attributes, like:
This solution is built with a combination of three core features of Profields:
If you want to use the same approach, you’ll need the scripts, of course: here they are.
Once this picture is ready, it’s easy to spot problems and suggest next steps towards a standardized use of schemes. And as the settings are changed in the background, the gadget will update with the current information: taking periodic screenshots can work as a longitudinal report.
Of course, the work doesn’t stop there. The audits we do at our clients have three main pillars:
With these three elements, we make sure that we automate information gathering for the tool while we still listen to the people who are actually involved in the project.
What we typically see when we deploy this solution is this:
Very often this is only the first phase in a long project that can differ in nature, for example:
While the path to standardization will be very different in each of these scenarios and our recommendations for one customer will not work for another, at the start we always put the automated audit. It helps to have conversations and to keep information inside Jira.
Feel free to drop your comments or feedback in this article, we’ll be using it to improve our knowledge base and tweak the solution. Possibly also to collect requirements for Profields!
Capi _resolution_Marketplace Partner