Once you've "Connected" your external apps to JIRA and Confluence, it's time to build a simple custom add-on to tune JIRA or Confluence to your company's needs. Learn how to quickly write and deploy a Connect add-on for internal use.

1. Luke Kilpatrick • Developer Program Manager • Atlassian • @lkilpatrick
“Hacking" JIRA and Confluence Cloud
Deploying your add-on

2. What do you need?

3. How an Atlassian Connect Add-on Works
Who's Looking for JIRA Cloud

4. The High Velocity
Web Framework
For Java and Scala
Toolkits
Coming Soon

6. Dynamic vs Static Add-ons
Dynamic Static!
• Server Side
• REST Calls
• Webhooks
• Dynamic Content
• Performance Concerns
!
• Client side
• REST Calls
• Easy hosting options
• Less Complex

7. How an Atlassian Connect Add-on Works
Who's Looking for JIRA Cloud
atlassian-­‐connect.json
descript file

8. Public vs Private
!
• Available in marketplace for install
by any admin
• Promotions
• Can make $$
!
• Internal use
• Development
Private Public

15. Going Public!

17. #atlassianKey takeaways:
• Robin Fernandes, AtlasCamp Session:
https://www.atlassian.com/atlascamp/2014/wednesday/building-production-ready-
connect-add-on
• Patrick Streule, AtlasCamp Session:
https://www.atlassian.com/atlascamp/2014/thursday/building-connect-add-on-with-
own-stack
• Who’s Looking - Play Framework -
https://bitbucket.org/atlassian/whoslooking-connect/src
• Who’s Looking - Static Javascript - https://bitbucket.org/atlassianlabs/atlassian-
connect-whoslooking-connect-v2/overview
• developer.Atlassian.com
Luke Kilpatrick • Developer Program Manager • Atlassian • @lkilpatrick