We successfully migrated over 100 projects and 5 million issues from several disparate Jira instances into one centralized platform. Jira now serves as the true end-to-end planning and tracking tool for all our teams.
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Happy Jira Admin Day - Looking back when I was just a standard JIRA user and I thought Jira is just a ticketing tool but I have come a long way in understanding that it's way more than that and this year I got my Administration expert batch for Jira cloud.
I just love working on automations and there hasn't been a day where I have not visited the global automations page and writing some cool automations to help my users :)
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
I became a Jira admin at my previous job almost by accident... but ended up really enjoying it! π Suddenly I was managing Jira, Confluence, JSM, and JPD, giving trainings to new teammates, and sharing all the shiny new Cloud features with the team βοΈ
Fast-forward to now: I've moved into a role as an Atlassian service team lead, where I get to combine all that admin knowledge with leading a team. Still learning every day, but I love helping others understand the tools, solve weird issues, and make their lives a bit easier through Jira magic πͺ
One of my wins this year has been finally getting comfortable with Assets in JSM. It felt like a beast at first, but now I canβt imagine managing service operations without it!
Happy Jira Admin Day to all the fellow button-clickers, scheme-fixers, and automation-builders out there! π
I'm in a new role in a new company this year. While most of the company uses team-managed projects, I've been thrilled to guide new teams to use Jira for organizing their work! The newest teams to join me in Jira are managing content. So far, they're LOVING Jira! π
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
We had an acquisition that brought a whole new service line with ~30 projects in progress for different clients, and I was able to build out their infra in about 1 week thanks to JSM!
I'd also like to shout out @Bill Sheboy for being an awesome resource to me (and others!) here in the community!
Started in Jira as an admin in 2014 and have built my career around it!
Who would of thought, that couple of smart dudes (Mike and Scott) wanting to get out of wearing a suit to work would have created such a break-through in ticket tracking tools!
My win is starting my series on JSM Tips and Tricks:
I am eternally grateful to Chaya Pick, our team's sole Jira admin. She builds beautiful workflows and boards and is constantly changing/tweaking/updating based on feedback from a wholly ungrateful user base! We would not get work done at our company without the work she does for us!
Of course β hereβs a revised version without explicitly mentioning Compass or Booking.com:
This year I've been focused on optimizing large-scale Jira instances across multiple departments after a major migration.
From building scalable project templates to fine-tuning permissions, automations, and reporting, the goal was always to make Jira intuitive and powerful for end users.
It's been rewarding to see teams adopt the improvements and rely on Jira as their central planning and tracking hub.
Here's to all the admins turning complexity into clarity every day!
This year has been mixed with some reversions to old processes that seemed to work better and also some adoption of new practices and tools that really sent us off at a fast pace toward our future. The biggest thing this year has been the implementation and adoption of the Xray Test Management app, building out the training materials required for it, adapting workflows and fields and permissions to match the app's needs, and ensuring literally thousands of test cases are tracked and documented properly. Big win for our organization, moving from spreadsheets tracking our test results to keeping the results aligned with the Jira work items they are associated to.
The past five years have been nothing short of an incredible journey.
We went from 98 Jira admins to just 3βstreamlining operations and rediscovering the power of simplicity. We reimagined our overlapping roles into a crisp, clear set of responsibilities that empowered teams and boosted collaboration. What was once a custom jungle of permissions is now a sleek ecosystem of common permission schemesβmanageable, scalable, and secure.
We reined in the chaos of priorities, replacing a fancy buffet of labels with four that truly matter: Low, Medium, High, and Critical. And when it came to infrastructure, we didnβt just migrateβwe evolved. From cloud to cloud, and from servers to the cloud, every move brought challenges, but even greater learning.
Now, as I face down the beast that is the "status" field, with its options sprawling like stars in the sky, and scrutinize app usage reports with a sharp eye for cost-cutting, I know this journey has been worth every step. With Rovo in sight, Iβm excited to take on whatβs next.
One of my big wins this year has been to migrate my team from a kanban process to a sprint process, which included an entirely new format to our Jira projects (in fact, moving from one team-managed project to many company-managed projects). With this change, I embarked on JMWE validators and post functions in order to both keep our work flowing properly with all the required data and to keep our automations below our monthly limit. Even though I've been working with Jira for nearly 10 years, my admin skills -- mostly self-taught -- are more on the beginner/intermediate level.
My Jira Admin challenge/accomplishment so far this year was converting ~1800 issues used to hold facilities information into Assets in Jira/JSM DC. The issues were entwined in so many ways with other capabilities in Jira; as linked issues, with data being pulled and pushed between them and their linked issues through Workflow and Automations, with ScriptRunner Listeners pulling using their data in custom notifications, and so on.
Not only did I have to convert the issues themselves into assets, I had to ensure that everything continued to work as before which included
Linking the new assets to the same other issues as the original facilities issues - that was hundreds of thousands of links!
Updating and replacing Automation Rules so they would continue to work as expected while referencing assets instead of issues
Updating and replacing functionality in workflows so they would continue to work as expected while referencing assets instead of issues
Updating Listeners that sent email notifications for issues to pull information from Assets linked to those issues
Writing scripts to migrate Comments and Attachments from the facilities issues to the corresponding new Assets
As part of this process I also wrote scripts to
shift through the comments on the facilities issues and delete almost 200k of useless comments
identify and delete duplicate attachments from the facilities issues
collect data from each facilities issue for fields that were not going to become asset attributes, and post that information to a comment for each asset.
Happy Jira Admin Day! π I hope you have a great day Jira admins! My biggest wins this year are:
Reducing automations excecution times in more than 20 automations to improve the general performance for JSM and JSW. Script more than 10 useful groovy scripts that also include some integrations to automate business servers actions. Following next, is the plan to reduce the unnecessary objects use in Assets to reduce billing.
Being a Jira admin means constantly being on the front lines of transformationβconnecting people, processes, and technology to deliver scalable, secure, and intelligent solutions.
Over the past year, Iβve had the opportunity to:
π Automate complex approval and decision-making workflows;
π‘ Redesign forms and processes to improve user experience and operational efficiency;
π Conduct strategic analyses to support cost reduction and enhance data visibility;
π€ Integrate artificial intelligence to accelerate delivery and free up time for what really matters;
π And of course, collaborate with multiple teams to promote sustainable and governed use of Jira.
It's truly rewarding to see how our work as admins directly impacts the success of teams. Kudos to everyone whoβs part of this daily mission to keep Jira running smoothly, securely, and delivering real value to the business! ππ§
I used the Jira Admin feature to set up the overall setup of a project I started in January of this year. The project is now approaching successful completion, and the AI features are making my work easier, especially the ability to generate JQLs and automate them, as they are now more accurate than before.
I look forward to become better admin with the rest of 2025's amazing features.
Happy Jira Admin Day to All Admins! I am grateful for @Fabio Genovese _ArtigianoDelSoftware_, who always motivates me to learn new things and move forward. I've learned a lot in 2025, especially JPD, Asset, APIs, and achieved 3 certifications.
One of my biggest milestones this year was successfully leading the migration from JIRA Data center to JIRA Cloud for one of our client. It was quite a challenging projectβcoordinating with multiple teams, cleaning up legacy configurations, and ensuring minimal downtime.
We used JIRA Cloud Migration Assistant, planned in phases, and did thorough UAT with stakeholders. The best part? After go-live, performance improved, and the teams loved the new UI and advanced automation capabilities!
Post-migration, I also helped build custom dashboards and automation rules that were not possible on Data Center, and the feedback from leadership has been really positive.
Definitely one of the most satisfying experiences in my Jira Admin journey.
back in 2016 my manager came to me and said: we have won a project and it is about DevOps tool chain. I was a software developer and didn't really like setting up tools and processes for others, I just wanted to CODE. Going through Jira screens, screen schemes, issue type screen schemes π and I felt challenged. 9.5 years later, I am still around and proud of being a Certified Atlassian Administration expert
From Curious User to Confident Jira Admin: My Journey
My journey with Jira began not as an administrator, but as a curious user trying to make sense of workflows, boards, and issue types. At the time, I was working in IT project coordination, and Jira was just one of many tools in our tech stack. But something about its flexibility and potential to streamline chaos drew me in.
I started asking questionsβwhy are our workflows so clunky? Can we automate status updates? Why are users struggling with permissions? Soon, I was not just asking questions, but answering them. I took on small admin tasksβtweaking screens, updating permissions, cleaning up custom fields. It was like learning a new language that helped teams work smarter.
Over time, I formalized my knowledge through Atlassian courses, community chats and hands-on practice. I began redesigning workflows to reflect real processes, introduced automations to cut down repetitive tasks, and created dashboards that actually told a story. One of my proudest moments was consolidating multiple, redundant projects into a unified structureβreducing confusion and increasing adoption.
Now, as a jira Administrator, I donβt just manage a tool, I empower teams.
I am sure for most of them, that this journey is ongoing, with every Atlassian update and team challenge bringing new opportunities to learn and improve. Iβm glad I followed my curiosityβbecause it led me to a role where I can make a real impact every day.
This year has been a great learning journey for me as a Jira Admin. I worked on cleaning up Jira custom fields and labels using Rovo and Forge β where an AI agent finds whatβs not needed, creates a work item, and then Forge helps remove it automatically. This really helped in keeping Jira neat and faster.
I also used PowerShell scripts and Atlassian Admin APIs to automate user group checks, product access, and cleanup tasks. It saved me a lot of manual work.
One of my proudest wins was finding a way to remove paid apps like JMWE and JSU by replacing them with built-in Jira automation, helping the company save costs.
Iβm always learning and sharing on LinkedIn and in the Atlassian Community, posting daily tips and use cases to help others too.
Happy to be part of this amazing community. Thanks Atlassian Community for this day to recognize our work!
One of the key wins this year has been driving greater governance and standardization across the platformβespecially during the phase of divesting redundant functionalities and apps. By streamlining our Jira environment, helping the stakeholders focus on what truly adds value, creating a win-win for both users and the organization.
Cheers to all Jira Admins who are continuously leveling up and transforming Jira into a true end-to-end planning and tracking tool for their teams!
This past year, as a Jira admin atTD SYNNEX, I had the incredible opportunity to lead a project that started as a local initiative and evolved into aglobal success story.
I was responsible fordesigning and structuring the entire Jira project for the Marketing team in Brazil, building workflows, automations, and integrations that brought agility, visibility, and collaboration to the team. The results were so impactful that the model wasadopted globally, becoming a reference across the company.
Seeing something I built with such care and strategy scale worldwide has been, without a doubt, my proudest moment as a Jira admin in 2025. π
69 comments