Loading...
「ツール」は右上に移動しました。
利用したサーバー: wtserver3
2いいね 16回再生

Jira Admin Secrets: How to Fix the Mess You Didn’t Know You Had

Is your Jira instance secretly a mess? 😬
You’re not alone — and you’re probably missing out on powerful tools, better performance, and serious time savings.

In this episode of Atlassian Everything, we sit down with Jimmy Seddon, a seasoned Jira admin with over a decade of experience managing Atlassian tools at scale. From 900 custom fields to hidden analytics goldmines, Jimmy shares the lessons every team needs to hear — but most learn the hard way.

🔍 What you'll learn:
✅ The biggest mistakes Jira admins make (and how to avoid them)
✅ How to clean up your instance without breaking everything
✅ What features you're paying for — but not using
✅ Why enterprise teams really need more than one admin
✅ And yes… the future of Data Center 😱

00:00 – Welcome & Setup
00:16 – Why Your Tools Deserve Real Investment
01:04 – Jimmy’s Journey: From QA to Jira Wizard
02:04 – What It’s Really Like Working at Arctic Wolf
03:03 – One Team, All the Tools — What Jimmy Manages
04:06 – Cloud vs. Data Center: The Honest Breakdown
05:22 – Why We Upgraded to Enterprise (And Never Looked Back)
06:33 – Performance Myths: What Slows Jira Down (and What Doesn’t)
08:37 – 900 Custom Fields?! Managing Jira Without the Chaos
11:19 – Do You Really Need That Field? How to Say No Smartly
13:01 – Why Every Enterprise Needs a Real Jira Admin Team
15:18 – Software ≠ Magic. Why Tools Need TLC
16:34 – When 4 Hours of Downtime Changed Everything
18:25 – Will Data Center Survive? Jimmy’s Bold Prediction
20:22 – What No One Tells You About Cloud Migrations
24:10 – The Most Underrated Jira Features You’re Not Using
26:09 – Jira Assets: Cool Power Feature or Overlooked Tool?
29:36 – What Happens After Atlassian Acquires a Tool
31:30 – Has Atlassian Forgotten About Trello?
31:38 – Final Advice: What Every Jira Admin Needs to Hear

📌 Subscribe for next episodes on Jira, Confluence, automation, and more!
💬 Got a Jira mess of your own? Drop your questions in the comments — we might cover it next epi

コメント