Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Intro - How to Build an Atlassian Add-on

Intro - How to Build an Atlassian Add-on

Atlassian User Group - Austin Texas
July 2017

Hector Benitez

July 17, 2017
Tweet

More Decks by Hector Benitez

Other Decks in Technology

Transcript

  1. What can I do with add-ons? • JIRA - Issues

    with Web Views • Confluence - Macros, Blueprints, look and feel • Bitbucket - Webhooks • Hipchat - Commands, Bots? • Trello - Powerups
  2. Cloud vs Server • Cloud - NodeJS, ACE by Atlassian,

    iframe inside the page. Needs and uses Internet. REST API • Server - Java, Atlassian SDK & Sample Add-ons, inside the page. Internet is not a must. Internal API. Needs to handle versions. https://developer.atlassian.com/ https://atlassian.design/
  3. • Most powerful Atlassian app. • More vendors. • Cloud:

    No communication with Confluence • Macros living inside pages. • Custom content. • Missing API’s, content is the key
  4. • A lot of free users. • A lot of

    opportunities • Free Add-ons? • Use the Sidebar and custom content • No Bots? • Free Add-ons?
  5. • Just HTML, CSS & Javascript • Should respond in

    1 sec • Power-ups does not auth users • No Marketplace https://www.youtube.com/watch?v=mb_8mLf-KRY&index=13&list=PLaD4FvsFdarS4deAMRe d5bIEDtxxomemZ
  6. Third Party • Auth via OAuth or Add-ons • Focused

    on the Cloud Stand.bot - http://softwaredevtools.com/stand-bot/