How to Join the “JIRA 1M Issues” Club

CLAUDIO OMBRELLA• SENIOR MANAGER ENGINEERING SYSTEMS AND INFRASTRUCTURE• AUTODESK INC• @CLAUDIOOMBRELLA

Agenda I N T R O D U C T I O N - H I S T O R Y

S T A T I S T I C S

C H A L L E N G E S - P R O J E C T S

T A K E A W A Y

Do you know?

Do you know AutoCAD?

Autodesk in a Nutshell • Founded in 1982

• 7800+ employees

• 140 products in 18 languages

• 19 Academy Award winners for Best Visual Effects

• Millions of professional and consumer users

• Revenue: 2.4 billion FY16

• Architecture, Engineering, Environment, Mechanical, Science, Computer Graphics and Animations

Visit us at Autodesk Gallery One Market St. San Francisco

What about You?

How Large is your JIRA Instance?

Will JIRA work with 1M+ Issues?

✔YES!

Will it work in your organization?

Depends on 5 Challenges!

History

2005 “The Year We Made Contact”

JBOSS Support Site

2007 First Adoption

7884 issues and 9 projects in 1 year

2008 Localization Services

Migrates Lotus Notes to JIRA Integrates Test Automation via SOAP

2009 Global Engineering

Adopts JIRA

2012 First record

JIRA 300,000 Issues Running on a VM

2015 New Record!

JIRA 1,000,000+ Issues

Statistics

Project Creation

Issue Creation

Issue Creation

In a Single Day

1,500+ 1,500+

4,600+

Users Access Issues Added

Issues Updated

In a Single Month

2,800+ 14,000+

34,000+

Users Access Issues Added

Issues Updated

2015 YTD

4,400+ 190,000+

393,000+

Users Access Issues Added

Issues Updated

5 Challenges you need to manage

#1 - Culture First – Systems Last

Corporate Ethos

Collaboration

Transparency

Processes

Governance

Efficiency

Technology

Support Business

Reliability

Adoption

Retention

#1a – JIRA - Adoption

Features Processes-Performance Cost

Workflow

Custom Fields

Plugins

Customizations

Administration

Software Upgrade

Consolidation of legacy systems

High Value

Low Cost

ADOPTION

Collaboration

Usability

Confluence

Perforce

GitHub

#1b JIRA Retention

Processes-Performance

Administration

Software Upgrade

Consolidation of legacy systems

Features

Workflow

Custom Fields

Plugins

Customizations

Collaboration

Usability

Confluence

Perforce

GitHub

Cost

High Value

Low Cost

RETENTION

#2 “In my empire

the sun never sets”

Philippe II of Spain

“At Autodesk

the sun never sets”

#3

#4 Focus on

5% missing features

#5 ”I heard that…”

Syndrome

Projects

Trac to JIRA Migration - DONE

• 100+ users

• 15,000 Issues

• Challenges:

• At that time the importer was not supporting encoded attachments path in Trac. A separate tool was written to work around this issue and we used JELLY script to attach the files.

JIRA to JIRA - DONE

• 1000+ users over 3 instances

• 300,000 Issues

• Challenges:

• Customize the target instance

• 2)Rename users to match LDAP names

• 3)Plan and run the test migration several times in staging instance

• 4)Encountered ranking issues after migration, rank balancing job more time than expected.

Lotus Notes to JIRA - DONE

• 250+ users

• 8,000 Issues

• Challenges:

• Write an automation that outputs Notes information and attachments including comments and its timestamps and import it on JIRA using Jelly Script

Bugzilla to JIRA - DONE

• 80+ users

• 18,000 Issues

• Challenges:

• Uploading this massive amount of data and its respective attachments

TFS to JIRA – Work in Progress

• 100+ users (1 out of 14 product lines)

• 3000 Issues

• Challenges:

• No migration tool. We internally built a tool for this purpose

• Retain inline images in TFS: need to convert the rich text to wiki markup

• Get the history from TFS and write it as a comment in JIRA

Trello to JIRA – Work in Progress

• 50+ users

• 4000 Issues

• Challenges:

• We are discovering them

RALLY to JIRA - Preparing

• 300+ users

• 35000 Issues

• Challenges:

• We are discovering them

System Performance

Run JIRA on Hardware and Linux

• 40 cores

• 128 GB RAM

• SSD Storage

Take Away

Pay attention to the cultural shift

Systems and people must naturally fit together

Rationalize the proliferation of systems

It's not the tools that you have faith in—tools are just tools. They work, or they don't work. It's people you have faith in or not…!

S T E V E J O B S – A P P L E

“ ”

Claudio Ombrel la• Senior Manager Engineering Systems and Infrastructure • Autodesk inc • @claudioombrel la

Thank you!