What started in 2008 as a team of 10 developers using JIRA has grown into an enterprise solution supporting over 11,400 users. Join Brian and Michael from Cerner for tips on overcoming the challenges of scaling JIRA. You'll learn how considering configuration, usage, and hardware can prevent outages and support a rapidly growing development environment.

1. Scaling JIRA: Challenge
Accepted
BRIAN WALLACE • VICE PRESIDENT • CERNER CORPORATION • @WALLACEBRIAN
MIKE DAMMAN • KNOWLEDGE ARCHITECT • CERNER CORPORATION • @MJDAMMAN

3. Our Environment…
• Issues – 444,783
• Projects – 433
• Custom Fields – 928
• Workflows – 188
• Attachments – 193,933
• Comments – 1,211,080
• Issues – 561,763
• Projects – 466
• Custom Fields – 139
• Workflows – 14
• Attachments – 155,069
• Comments – 1,262,905
• Issues – 382,613
• Projects – 516
• Custom Fields – 1,116
• Workflows – 363
• Attachments – 91,251
• Comments – 768,512
1 2 3(Data Center)
2008! 2010! 2012! 2014!
1 2&3

4. Lesson 1: Stay Current
2008! 2010! 2012! 2014!
1 2&3
6.3.123.13

5. Lesson 2: Standardize Where Possible
2008! 2010! 2012! 2014!
1 2&3
6.3.123.13

6. Lesson 2: Standardize Where Possible
GETTING STARTED WITH JIRA SCALE - SCALING JIRA
“The configuration attributes that affect JIRA speed the
most are custom fields and workflows. In particular, they
impact the time of the create issue operation, which is one
of the most important for JIRA users. That means it is still a
good practice to keep your JIRA configuration lean.”!
2008! 2010! 2012! 2014!
1 2&3
6.3.123.13

7. Lesson 2: Standardize Where Possible
• Issues – 444,783
• Projects – 433
• Custom Fields – 928
• Workflows – 188
• Attachments – 193,933
• Comments – 1,211,080
• Issues – 561,763
• Projects – 466
• Custom Fields – 139
• Workflows – 14
• Attachments – 155,069
• Comments – 1,262,905
• Issues – 382,613
• Projects – 516
• Custom Fields – 1,116
• Workflows – 363
• Attachments – 91,251
• Comments – 768,512
1 2 3(Data Center)
2008! 2010! 2012! 2014!
1 2&3
6.3.123.13

8. Lesson 3: Monitor Activity
2008! 2010! 2012! 2014!
3.13 6.3.12
1 2&3

9. Lesson 3: Monitor Activity
2008! 2010! 2012! 2014!
3.13 6.3.12
1 2&3

10. Lesson 3: Monitor Activity
2008! 2010! 2012! 2014!
3.13 6.3.12
1 2&3

11. Lesson 3: Monitor Activity
2008! 2010! 2012! 2014!
3.13 6.3.12
1 2&3

12. Lesson 4: Educate Users on JQL
project = ACME AND issue in parent("status in (verified, released, closed, deployed)")
AFTER
issue in parent("project = ACME AND status in (verified, released, closed, deployed)")
BEFORE
2008! 2010! 2012! 2014!
3.13 6.3.12
1 2&3

13. Lesson 5: Evaluate Plugins
2008! 2010! 2012! 2014!
3.13 6.3.12
1 2&3

14. Lesson 5: Evaluate Plugins
“COMMON SENSE:!
Just because you
can, doesn’t mean
you should.”!
http://www.psychicdonut.com/wp-content/uploads/2014/06/common-sense-just-because-you-can-doesn-t-mean-you-should.jpg
2008! 2010! 2012! 2014!
3.13 6.3.12
1 2&3

15. Lesson 5: Evaluate Plugins
2008! 2010! 2012! 2014!
3.13 6.3.12
1 2&3

16. Lesson 6: Take Advantage of High Availability
2008! 2010! 2012! 2014!
3.13 6.3.12
1 2&3

17. Lesson 6: Take Advantage of High Availability
2008! 2010! 2012! 2014!
3.13 6.3.12
1 2&3

18. Lesson 6: Take Advantage of High Availability
2008! 2010! 2012! 2014!
3.13 6.3.12
1 2&3

19. Lessons Learned
1. Stay Current
2. Standardize Where Possible
3. Monitor Activity
4. Evaluate Plugins
5. Educate Users on JQL
6. Take Advantage of High Availability
2008! 2010! 2012! 2014!
3.13 6.3.12
1 2&3

20. Thank you!
B R I A N W A L L A C E • V I C E P R E S I D E N T • C E R N E R C O R P O R A T I O N • @W A L L A C E B R I A N
M I K E D A M M A N • K N O W L E D G E A R C H I T E C T • C E R N E R C O R P O R A T I O N • @ M J D A M M A N