AtlasCamp US 2012 Keynote, Jean-Michel Lemieux
Upcoming SlideShare
Loading in...5
×
 

AtlasCamp US 2012 Keynote, Jean-Michel Lemieux

on

  • 3,281 views

Jean-Michel Lemieux, VP of Engineering Update on the Atlassian Developer Network, new product releases, Marketplace updates, and more.

Jean-Michel Lemieux, VP of Engineering Update on the Atlassian Developer Network, new product releases, Marketplace updates, and more.

Statistics

Views

Total Views
3,281
Views on SlideShare
1,451
Embed Views
1,830

Actions

Likes
0
Downloads
14
Comments
0

8 Embeds 1,830

http://www.atlassian.com 1540
https://www.atlassian.com 171
https://wacdev.internal.atlassian.com 72
http://lanyrd.com 21
http://magnolia-staging.private.atlassian.com 21
http://localhost 3
https://wacstg.internal.atlassian.com 1
https://fr.atlassian.com 1
More...

Accessibility

Categories

Upload Details

Uploaded via as Apple Keynote

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • \n
  • Welcome, I’ve got the best job at Atlassian. Preparing these slides really got me excited about all the innovation that is going on by our teams and also in our ecosystem. Sometimes you get lost in the details of each release.\n\nYou may of noticed that Scott isn’t here. He sends his regrets but he had to cancel his trip at the last minute because of ilness. He waited until the very last minute, and was terribly hard to made the decision.\n
  • Camp is special for us. This is not a user conference but a gathering of people who’s main mission is to deliver value to our customers. To make them awesome.\n\nTo do this, we share a lot more than we would normally with our end users. We do this because YOU have to know what’s going on behind the scenes.\n\nWe will be providing sneak peeks today, probably more than we have in the past, and would prefer if you hold off on the “tweets” and instead take notes and ask us questions during the week. \n\nAlso, roadmaps and plans may change, so the dates we are providing are our best guess at the moment and may change.\n\n\n
  • We flew our top shot developers from Sydney and bused another handful from SF to come and spend time with you at Camp. \n\nIn total we’ve got 38 Atlassian’s here, which means that you can gang up on us with with a 4:1 ratio. Please abuse of our knowledge, pry everything out that you can out of us, we are looking forward to being busy these two days.\n
  • This is our 5th Camp or 6th if we count the European event in March. We started with only 20 people at the first AtlasCamp while this year, with the mid-year event we’ve had more than 350 people attend our developer events between Sept 2011 and Sept 2012!\n\nYou are our closest friends and we invest a lot in making YOU successful which in turns makes our customers successfull by helping teams everywhere build stuff.\n\nWe also recognise that some of you have travelled from Europe and around the world for Summit which was only 3 months ago.\n
  • Now what about you? \n\nEveryone stand-up and let’s start the day with a bit of fun. If this is your first AtlasCamp please sit down, if this is your second sit down, etc... at the end we will have the hardcore, die-hard supporters. A huge thanks for supporting us through the years, giving all the great feedback, and building addons that help make our combined customers more productive on their teams. \n\nAnd for those that haven’t been around, you now know who to ask questions and connect with.\n
  • It’s challenging to give an overview when so much is happening. With almost 250 strong in our product development team now, it’s not a lack of things to highlight.\n\nWe have a lot to cover, so let’s get rolling.\n
  • Before we jump into the products, let’s review some of the highlights from our ecosystem.\n
  • So just how big has the year been in terms of releases we’ve been adding to the ecosystem? \n\nWe’ve released 33 major releases of our products from August 2011 to August 2012 and totalled 234 total releases which includes minor releases. So how does this help you? \n\n* It’s a great forcing function for us to get better with apis - as we can’t break each other within Atlassian and our plugins.\n\n* We continue to improve our speed at reacting to customer feedback, not just in products but in our supporting services such as marketplace, upm, and the sdk.\n\n* We are writing more and more in plugins ourselves. This means dog-fooding APIs and the tool chains.\n\n
  • So just how big has the year been in terms of releases we’ve been adding to the ecosystem? \n\nWe’ve released 33 major releases of our products from August 2011 to August 2012 and totalled 234 total releases which includes minor releases. So how does this help you? \n\n* It’s a great forcing function for us to get better with apis - as we can’t break each other within Atlassian and our plugins.\n\n* We continue to improve our speed at reacting to customer feedback, not just in products but in our supporting services such as marketplace, upm, and the sdk.\n\n* We are writing more and more in plugins ourselves. This means dog-fooding APIs and the tool chains.\n\n
  • So just how big has the year been in terms of releases we’ve been adding to the ecosystem? \n\nWe’ve released 33 major releases of our products from August 2011 to August 2012 and totalled 234 total releases which includes minor releases. So how does this help you? \n\n* It’s a great forcing function for us to get better with apis - as we can’t break each other within Atlassian and our plugins.\n\n* We continue to improve our speed at reacting to customer feedback, not just in products but in our supporting services such as marketplace, upm, and the sdk.\n\n* We are writing more and more in plugins ourselves. This means dog-fooding APIs and the tool chains.\n\n
  • So just how big has the year been in terms of releases we’ve been adding to the ecosystem? \n\nWe’ve released 33 major releases of our products from August 2011 to August 2012 and totalled 234 total releases which includes minor releases. So how does this help you? \n\n* It’s a great forcing function for us to get better with apis - as we can’t break each other within Atlassian and our plugins.\n\n* We continue to improve our speed at reacting to customer feedback, not just in products but in our supporting services such as marketplace, upm, and the sdk.\n\n* We are writing more and more in plugins ourselves. This means dog-fooding APIs and the tool chains.\n\n
  • You’ve also been busy, we hosted our yearly addon competition and the number of entries increased by 43% going from 60 entries in 2011 to 94 this year and we handed out $45K of prize money.\n
  • You’ve also been busy, we hosted our yearly addon competition and the number of entries increased by 43% going from 60 entries in 2011 to 94 this year and we handed out $45K of prize money.\n
  • You’ve also been busy, we hosted our yearly addon competition and the number of entries increased by 43% going from 60 entries in 2011 to 94 this year and we handed out $45K of prize money.\n
  • You’ve also been busy, we hosted our yearly addon competition and the number of entries increased by 43% going from 60 entries in 2011 to 94 this year and we handed out $45K of prize money.\n
  • You’ve also been busy, we hosted our yearly addon competition and the number of entries increased by 43% going from 60 entries in 2011 to 94 this year and we handed out $45K of prize money.\n
  • Although there were tons of great entries some of the key take aways from the winners and runner-up was the quality of their addons. They solved real user problems and opportunities and their authors clearly put in the extra mile to have a great slick looking design and marketing.\n\nBadgr is a free plugin for Stash built by Stefan Kohler. Badgr makes committing code fun and addicting. With Badgr, your commits can turn into badges that reward your hard work. Our judges loved this plugin because of Stefan Kohler’s great sense of design, marketing, and great implementation.\n\nThe Best Overall Add-on this year went to META-INF in Hungary for their Bug Watcher JIRA plugin. Our judges liked this plugin simply because it implements key features of 3 highly voted issues on the JIRA issue tracker. This plugin basically allows you to watch issues in a very flexible way... like watching an entire project, bulk watching, or by creating filters.\n
  • Although there were tons of great entries some of the key take aways from the winners and runner-up was the quality of their addons. They solved real user problems and opportunities and their authors clearly put in the extra mile to have a great slick looking design and marketing.\n\nBadgr is a free plugin for Stash built by Stefan Kohler. Badgr makes committing code fun and addicting. With Badgr, your commits can turn into badges that reward your hard work. Our judges loved this plugin because of Stefan Kohler’s great sense of design, marketing, and great implementation.\n\nThe Best Overall Add-on this year went to META-INF in Hungary for their Bug Watcher JIRA plugin. Our judges liked this plugin simply because it implements key features of 3 highly voted issues on the JIRA issue tracker. This plugin basically allows you to watch issues in a very flexible way... like watching an entire project, bulk watching, or by creating filters.\n
  • Although there were tons of great entries some of the key take aways from the winners and runner-up was the quality of their addons. They solved real user problems and opportunities and their authors clearly put in the extra mile to have a great slick looking design and marketing.\n\nBadgr is a free plugin for Stash built by Stefan Kohler. Badgr makes committing code fun and addicting. With Badgr, your commits can turn into badges that reward your hard work. Our judges loved this plugin because of Stefan Kohler’s great sense of design, marketing, and great implementation.\n\nThe Best Overall Add-on this year went to META-INF in Hungary for their Bug Watcher JIRA plugin. Our judges liked this plugin simply because it implements key features of 3 highly voted issues on the JIRA issue tracker. This plugin basically allows you to watch issues in a very flexible way... like watching an entire project, bulk watching, or by creating filters.\n
  • Although there were tons of great entries some of the key take aways from the winners and runner-up was the quality of their addons. They solved real user problems and opportunities and their authors clearly put in the extra mile to have a great slick looking design and marketing.\n\nBadgr is a free plugin for Stash built by Stefan Kohler. Badgr makes committing code fun and addicting. With Badgr, your commits can turn into badges that reward your hard work. Our judges loved this plugin because of Stefan Kohler’s great sense of design, marketing, and great implementation.\n\nThe Best Overall Add-on this year went to META-INF in Hungary for their Bug Watcher JIRA plugin. Our judges liked this plugin simply because it implements key features of 3 highly voted issues on the JIRA issue tracker. This plugin basically allows you to watch issues in a very flexible way... like watching an entire project, bulk watching, or by creating filters.\n
  • Although there were tons of great entries some of the key take aways from the winners and runner-up was the quality of their addons. They solved real user problems and opportunities and their authors clearly put in the extra mile to have a great slick looking design and marketing.\n\nBadgr is a free plugin for Stash built by Stefan Kohler. Badgr makes committing code fun and addicting. With Badgr, your commits can turn into badges that reward your hard work. Our judges loved this plugin because of Stefan Kohler’s great sense of design, marketing, and great implementation.\n\nThe Best Overall Add-on this year went to META-INF in Hungary for their Bug Watcher JIRA plugin. Our judges liked this plugin simply because it implements key features of 3 highly voted issues on the JIRA issue tracker. This plugin basically allows you to watch issues in a very flexible way... like watching an entire project, bulk watching, or by creating filters.\n
  • Although there were tons of great entries some of the key take aways from the winners and runner-up was the quality of their addons. They solved real user problems and opportunities and their authors clearly put in the extra mile to have a great slick looking design and marketing.\n\nBadgr is a free plugin for Stash built by Stefan Kohler. Badgr makes committing code fun and addicting. With Badgr, your commits can turn into badges that reward your hard work. Our judges loved this plugin because of Stefan Kohler’s great sense of design, marketing, and great implementation.\n\nThe Best Overall Add-on this year went to META-INF in Hungary for their Bug Watcher JIRA plugin. Our judges liked this plugin simply because it implements key features of 3 highly voted issues on the JIRA issue tracker. This plugin basically allows you to watch issues in a very flexible way... like watching an entire project, bulk watching, or by creating filters.\n
  • This year we’ve also created a dedicated team who’s mission is to help answer your development questions. \n\nWe currently get 350 questions a month on AAC related to development, 6 a day, and as you know many of them require looking at code samples and investigating and logging issues for the SDK or products. The team currently has a 80% answer rate with 40% of the questions being answered within an hour!\n\nWe are also planning the rollout of new changes to ACC to help guide and group development versus product questions. Thanks for all those have helped answer development questions on ACC!\n\nTransition & Recap: as we release more and more often so are you. we also realise that development support is critical to help us both keep up the pace and ensure that we build things together effectively.\n
  • This year we’ve also created a dedicated team who’s mission is to help answer your development questions. \n\nWe currently get 350 questions a month on AAC related to development, 6 a day, and as you know many of them require looking at code samples and investigating and logging issues for the SDK or products. The team currently has a 80% answer rate with 40% of the questions being answered within an hour!\n\nWe are also planning the rollout of new changes to ACC to help guide and group development versus product questions. Thanks for all those have helped answer development questions on ACC!\n\nTransition & Recap: as we release more and more often so are you. we also realise that development support is critical to help us both keep up the pace and ensure that we build things together effectively.\n
  • With 33 major releases this year there is definitely a lot to talk about about the products. But I’ve picked the highlights and areas that as a developer will impact how and what you build.\n
  • Before we jump into talking about the individual products, let’s talk about “user experience”. It’s something that we’ve been investing in a lot and are really excited about.\n\nWe’ve trippled our design team over the last year and taken a deep look at the user experience across all our products. \n\nYou haven’t seen the results just yet, but you’ll see them rolling out over the next 6 months. Given that YOU are a critical piece of the overall user experience of our products, we want to share our thinking and plans with you today.\n
  • We recently held an interview with a customer after which he sent us the following e-mail: \n\n“I hope your UI designer didn’t mind too much when I likened Confluence to “the config screen of my Linksys router”...?” \n\nWe have received frequent feedback like this from our customers, that our products look dated and the products are not consistent (visual and ux) between each other and even between addons.\n\nUser experience and design is not just about “pixel” pushing so we spent a lot of time reflecting about the kind of user experience we wanted to provide in our products but also the “feeling” and “character” we wanted our products to have. \n
  • You can recognize a BMW sports car regardless of the model or year? This is effective design at work. The design language establishes the visual vocabulary, relationships and hierarchies that allow diverse products to become recognizable and unified. \n\nThe outcome of our reflection is a set of design guidelines that include colors, fonts, common interaction patterns (how/when to user different controls and navigations for example), controls, and styling.\n\nThis still leaves the product and addon with a lot of creativity, but will help guide us and our ecosystem (eg, YOU) to take user experience into everything we build. And build out the Atlassian character commonly into our products.\n
  • We started applying the guidelines with the header. We wanted to simplify, help users get started, and not be afraid to admit that these are products and not websites. \n\n<< click to reveal new header >>\n\nAnd there you have it. It’s single line, has all the extension points, has a “call to action”, and we’ve extracted the important configuration and help menus.\n\nIt’s also a single line, which means that if a product has extra information it will be added to the page needing it instead of the header.\n\n\n
  • We started applying the guidelines with the header. We wanted to simplify, help users get started, and not be afraid to admit that these are products and not websites. \n\n<< click to reveal new header >>\n\nAnd there you have it. It’s single line, has all the extension points, has a “call to action”, and we’ve extracted the important configuration and help menus.\n\nIt’s also a single line, which means that if a product has extra information it will be added to the page needing it instead of the header.\n\n\n
  • We started applying the guidelines with the header. We wanted to simplify, help users get started, and not be afraid to admit that these are products and not websites. \n\n<< click to reveal new header >>\n\nAnd there you have it. It’s single line, has all the extension points, has a “call to action”, and we’ve extracted the important configuration and help menus.\n\nIt’s also a single line, which means that if a product has extra information it will be added to the page needing it instead of the header.\n\n\n
  • But there is more... the look at feel and function will be consistent between the products. Did you notice Bitbucket in there cool eh? I’ll get back to how we did that later. \n\nThere are “call to action” buttons for creating key artifacts in each product when it makes sense, common interaction patterns (eg, how buttons and dropdowns work).\n
  • Oh, and there is one more thing.\n\nOur users navigate between products, either they’ve installed several products or several instances behind the firewall or are in OnDemand and have our custom tabbed view as shown here.\n\nWe’ve taken all this into consideration, unified how install and ondemand will work...introducing the new app switcher.\n\nIt works everywhere, OnDemand and OnPremise in the same way and can be extended when integrating different applications.\n
  • Oh, and there is one more thing.\n\nOur users navigate between products, either they’ve installed several products or several instances behind the firewall or are in OnDemand and have our custom tabbed view as shown here.\n\nWe’ve taken all this into consideration, unified how install and ondemand will work...introducing the new app switcher.\n\nIt works everywhere, OnDemand and OnPremise in the same way and can be extended when integrating different applications.\n
  • Oh, and there is one more thing.\n\nOur users navigate between products, either they’ve installed several products or several instances behind the firewall or are in OnDemand and have our custom tabbed view as shown here.\n\nWe’ve taken all this into consideration, unified how install and ondemand will work...introducing the new app switcher.\n\nIt works everywhere, OnDemand and OnPremise in the same way and can be extended when integrating different applications.\n
  • Oh, and there is one more thing.\n\nOur users navigate between products, either they’ve installed several products or several instances behind the firewall or are in OnDemand and have our custom tabbed view as shown here.\n\nWe’ve taken all this into consideration, unified how install and ondemand will work...introducing the new app switcher.\n\nIt works everywhere, OnDemand and OnPremise in the same way and can be extended when integrating different applications.\n
  • The header is just the start for a refresh and applying the design guide. Today we are launching the Atlassian Design Guidelines.\n\nhttps://developer.atlassian.com/design/\n\nWe’d like to share a beta version of the Atlassian Design Guidelines with you today which cover controls, patterns and guidance on how to use them. It’s live, it shows example, tips, and is built using the same code that you’d put in our addon or product.\n\n\n
  • Here is an example of the vertical navigation, has usage instructions, and examples.\n
  • This really comes together when you see it applied to the products. Here is a sneak peek at Confluence 5.0.\n
  • This really comes together when you see it applied to the products. Here is a sneak peek at Confluence 5.0.\n
  • This really comes together when you see it applied to the products. Here is a sneak peek at Confluence 5.0.\n
  • ... and JIRA 6.0.\n
  • ... and JIRA 6.0.\n
  • ... and JIRA 6.0.\n
  • To accompagny the design guideline is a toolkit to make your life easier. You don’t have to use AUI, but it does make things easier. \n\nWe are really excited about the “flat pack” as it will allow you to use in your non-plugin based products, integrations, and websites. We are using the flat pack in Bitbucket, the design guidelines themselves are also built with the flat pack.\n\nhttps://developer.atlassian.com/display/AUI\n
  • To accompagny the design guideline is a toolkit to make your life easier. You don’t have to use AUI, but it does make things easier. \n\nWe are really excited about the “flat pack” as it will allow you to use in your non-plugin based products, integrations, and websites. We are using the flat pack in Bitbucket, the design guidelines themselves are also built with the flat pack.\n\nhttps://developer.atlassian.com/display/AUI\n
  • To accompagny the design guideline is a toolkit to make your life easier. You don’t have to use AUI, but it does make things easier. \n\nWe are really excited about the “flat pack” as it will allow you to use in your non-plugin based products, integrations, and websites. We are using the flat pack in Bitbucket, the design guidelines themselves are also built with the flat pack.\n\nhttps://developer.atlassian.com/display/AUI\n
  • The first products to ship will be in October with the new header in OnDemand and Bitbucket will implement the design guidelines using the AUI flat-pack.\n\nThere will be milestones along the way and with JIRA 6.0 and Confluence 5.0 in February the design refresh will be launched.\n\nWe want you to launch with us. Plugins can update immediately, learn the guidelines, use AUI, and follow our progress with the betas.\n
  • We just released Confluence 4.3 earlier this month and you probably saw us demo some of the features back at Summit. There are a TON of cool features in this release, and customers have been really excited about it. (stress: a lot of features, but as a developer this is what you can play with!)\n\nAnd what’s cool for you guys, is that 4.3 has a lot of features to hack.\n
  • \n
  • * Shihab will talk more about the APIs for Workbox Tasks and notifications\n* I just wanted to share with you a pretty cool CLI tools that one of our developers, Sam Tardif, did on top of the new Confluence tasks API\n* he wanted a quicker way to bulk manage tasks so he built this little tool...notice the \n* Sherif can also show you some cool ways that team calendars is pluging into notifications to help make your plugin more discoverable to end users.\n\nAdd shorter link\nhttps://extranet.atlassian.com/display/~stardif/2012/09/11/WorkBox+Command+Line+Tool\n
  • * Here’s another example of extending workbox notifications to make your plugin more \n* The Confluence team has been thinking of ways to make end users more aware of plugins that their admin installs for them.\n* So Team Calendars is using the workbox notifications API to notify users that their admin installed Team Calendars for them and that it’s ready to use.\n* Again, Shihab will talk more about these API’s in his talk.\n\n== Think about the experience of when to actually notify as the addon has to be configured. Think about feature discovery (a theme for the marketplace)\n
  • * We wanted to really control the mobile experience for Confluence, so we built a mobile web experience from the ground up to (i) make pages load fast, (ii) make it easy to navigate and (iii) to make content shine on a tiny screen.\n\n==> mobile rendering mode\n\n* We know that a lot of macros aren’t designed to work on a mobile device so we tightly restricted what macros would render in mobile in Confluence 4.3. We’re now working on mobile rendering mode for your macros so, say you output flash or something like that, you can provide a mobile render mode for your macro. That should be available in one the coming 4.3 bugfix releases.\n\n* We also know that some plugins want to hook into the left-hand navigation just like we do with notifications and tasks. Support for that is a little more experimental but come talk to me, Sherif, Shihab or Peggy if you want to learn more. Will be in 4.3.X.\n
  • Looking ahead, we’ve begun work on Confluence 5.0 which will give you guys a bunch of new features and APIs to work with. It’s implementing the design guidelines, new header, and a lot of user experience improvements. \n\nIn addition, we are also looking closely at how content is created and looking at how to make that easier...\n
  • Looking ahead, we’ve begun work on Confluence 5.0 which will give you guys a bunch of new features and APIs to work with. It’s implementing the design guidelines, new header, and a lot of user experience improvements. \n\nIn addition, we are also looking closely at how content is created and looking at how to make that easier...\n
  • We are calling this Apps.\n\nSo let me just dive a little bit into this “Apps” concept, we have planned for Confluence 5. \n\n“Apps” is the codename for the project - and it’s our solution to what we’ve been calling internally the “Blank page problem”. This is a common problem we often sighted as a hindrance to adoption. \n* It’s users asking what do I use Confluence for?\n* And a subsequent question is often how? \n\nThe problem is prevalent not only for evaluators but also the “100th” user that might join your organisation. And today, it takes someone like a “wiki champion” - which I’m sure many of you are, to show users the “How” and the “What”. \n\nSo Confluence “Apps” is really all about productising the use cases with the goals of showing people what they can create, how they can create it and helping them structure it. These use cases many if you are already familiar with: Using Confluence for meetings, documents, specifications, projects etc... \n\n---- CLICK\n\nSo why should you care? We’ll if you’re a commercial plugin developer, we’d LOVE to hear from you. The project is still in concept phase, so you can help us shape the solution. In addition, apps presents a new opportunity for you to create add-ons that make content creation experience for your macro or even new types of content first-class in Confluence. \n\n---- CLICK\n\nWe don’t have a talk for this as it’s still really early stages, but Sherif Mansour is here with us - the Product Manager for “Apps”, and he is looking to hear from you and maybe have some one-on-ones with many of you here, so if you are interested, grab him and have chat to him or email him. \n \nSherif - do you want to stand-up so people see what you look like, this really isn’t your photo! \n
  • We are calling this Apps.\n\nSo let me just dive a little bit into this “Apps” concept, we have planned for Confluence 5. \n\n“Apps” is the codename for the project - and it’s our solution to what we’ve been calling internally the “Blank page problem”. This is a common problem we often sighted as a hindrance to adoption. \n* It’s users asking what do I use Confluence for?\n* And a subsequent question is often how? \n\nThe problem is prevalent not only for evaluators but also the “100th” user that might join your organisation. And today, it takes someone like a “wiki champion” - which I’m sure many of you are, to show users the “How” and the “What”. \n\nSo Confluence “Apps” is really all about productising the use cases with the goals of showing people what they can create, how they can create it and helping them structure it. These use cases many if you are already familiar with: Using Confluence for meetings, documents, specifications, projects etc... \n\n---- CLICK\n\nSo why should you care? We’ll if you’re a commercial plugin developer, we’d LOVE to hear from you. The project is still in concept phase, so you can help us shape the solution. In addition, apps presents a new opportunity for you to create add-ons that make content creation experience for your macro or even new types of content first-class in Confluence. \n\n---- CLICK\n\nWe don’t have a talk for this as it’s still really early stages, but Sherif Mansour is here with us - the Product Manager for “Apps”, and he is looking to hear from you and maybe have some one-on-ones with many of you here, so if you are interested, grab him and have chat to him or email him. \n \nSherif - do you want to stand-up so people see what you look like, this really isn’t your photo! \n
  • \n\n
  • \n\n
  • \n\n
  • \n\n
  • You can think of the focus in JIRA over the last year as being along two main streams. And both are equaly important to all of you:\n\n* The Platform makes it easier and expands the ways to integrate with JIRA.\n* The user love is all about making it easier and simpler to work with issues and your team. \n\nThe “user love” theme is important because our goal is to provide more customer value and making it easier and faster to work with issues will be a big win for everyone. \n
  • Today I’ll focus on 3 main areas.\n\nOne thing to highlight before we move on, although we are evolving the user experience with features such as “inline edit” and “new search”, we’ve been stressing about how to make the evolution as painless for our ecosystem as possible. It’s actually pretty freaking awesome that “Inline” was backwards compatible, and written as a plugin!\n
  • JIRA 5.0 was released shorting after AtlasCamp last year. We spent a lot of effort with APIs with the goal of making it a lot easier for you to upgrade between releases. How many of you have used the plugin checkup to either move off private APIs? It will make your life easier, maintain one code base for all 5.X versions.\n
  • JIRA 5.0 was released shorting after AtlasCamp last year. We spent a lot of effort with APIs with the goal of making it a lot easier for you to upgrade between releases. How many of you have used the plugin checkup to either move off private APIs? It will make your life easier, maintain one code base for all 5.X versions.\n
  • JIRA 5.0 was released shorting after AtlasCamp last year. We spent a lot of effort with APIs with the goal of making it a lot easier for you to upgrade between releases. How many of you have used the plugin checkup to either move off private APIs? It will make your life easier, maintain one code base for all 5.X versions.\n
  • We’ve had over 1746 support issues logged and handled by Atlassian Support as a result of your addons causing problems in customer instances. \n\nA lot of these are related to large instances, performance, and scalability. We released two tools to help you make your addons better. The JIRA data collector and the Grinder test framework. Check them out and let’s work together to keep our customers instances stable and invest back those 5 SEs into more valuable customer support efforts!\n
  • We’ve had over 1746 support issues logged and handled by Atlassian Support as a result of your addons causing problems in customer instances. \n\nA lot of these are related to large instances, performance, and scalability. We released two tools to help you make your addons better. The JIRA data collector and the Grinder test framework. Check them out and let’s work together to keep our customers instances stable and invest back those 5 SEs into more valuable customer support efforts!\n
  • We’ve had over 1746 support issues logged and handled by Atlassian Support as a result of your addons causing problems in customer instances. \n\nA lot of these are related to large instances, performance, and scalability. We released two tools to help you make your addons better. The JIRA data collector and the Grinder test framework. Check them out and let’s work together to keep our customers instances stable and invest back those 5 SEs into more valuable customer support efforts!\n
  • We’ve had over 1746 support issues logged and handled by Atlassian Support as a result of your addons causing problems in customer instances. \n\nA lot of these are related to large instances, performance, and scalability. We released two tools to help you make your addons better. The JIRA data collector and the Grinder test framework. Check them out and let’s work together to keep our customers instances stable and invest back those 5 SEs into more valuable customer support efforts!\n
  • We’ve had over 1746 support issues logged and handled by Atlassian Support as a result of your addons causing problems in customer instances. \n\nA lot of these are related to large instances, performance, and scalability. We released two tools to help you make your addons better. The JIRA data collector and the Grinder test framework. Check them out and let’s work together to keep our customers instances stable and invest back those 5 SEs into more valuable customer support efforts!\n
  • * REST APIs in JIRA 5.0 helped remote developers create issues in JIRA, update issues in JIRA, find issues in JIRA,\n* How many of you have used JIRA’s REST API?\n* But there was still a hole in what you could do with JIRA REST. The nature of REST is inbound, and you may need your app to get updates from JIRA as soon as they happen.\n* Anytime you wanted an update on an issue that your application cared about, you had to poll JIRAs to figure out if something changed, either by keeping state, always writing over your local state, or querying changelogs and checking timestamps. \n\n\n
  • * REST APIs in JIRA 5.0 helped remote developers create issues in JIRA, update issues in JIRA, find issues in JIRA,\n* How many of you have used JIRA’s REST API?\n* But there was still a hole in what you could do with JIRA REST. The nature of REST is inbound, and you may need your app to get updates from JIRA as soon as they happen.\n* Anytime you wanted an update on an issue that your application cared about, you had to poll JIRAs to figure out if something changed, either by keeping state, always writing over your local state, or querying changelogs and checking timestamps. \n\n\n
  • * REST APIs in JIRA 5.0 helped remote developers create issues in JIRA, update issues in JIRA, find issues in JIRA,\n* How many of you have used JIRA’s REST API?\n* But there was still a hole in what you could do with JIRA REST. The nature of REST is inbound, and you may need your app to get updates from JIRA as soon as they happen.\n* Anytime you wanted an update on an issue that your application cared about, you had to poll JIRAs to figure out if something changed, either by keeping state, always writing over your local state, or querying changelogs and checking timestamps. \n\n\n
  • * REST APIs in JIRA 5.0 helped remote developers create issues in JIRA, update issues in JIRA, find issues in JIRA,\n* How many of you have used JIRA’s REST API?\n* But there was still a hole in what you could do with JIRA REST. The nature of REST is inbound, and you may need your app to get updates from JIRA as soon as they happen.\n* Anytime you wanted an update on an issue that your application cared about, you had to poll JIRAs to figure out if something changed, either by keeping state, always writing over your local state, or querying changelogs and checking timestamps. \n\n\n
  • Highlight in the code that the changelog has the delta and generally more than enough information that doesn’t require the receiver to have to call back to JIRA for most use-cases.\n
  • Highlight in the code that the changelog has the delta and generally more than enough information that doesn’t require the receiver to have to call back to JIRA for most use-cases.\n
  • Highlight in the code that the changelog has the delta and generally more than enough information that doesn’t require the receiver to have to call back to JIRA for most use-cases.\n
  • Highlight in the code that the changelog has the delta and generally more than enough information that doesn’t require the receiver to have to call back to JIRA for most use-cases.\n
  • Webhooks should be simple. \n\nBut, the power of JQL is amazing. It means that without a single code change to JIRA a remote integration or app can register a hook, update the JQL, and get notified of the deltas. All without polling and without any changes to JIRA!\n
  • While JIRA 5.0 focused on the platform and new APIs, JIRA 6.0 is focused on the JIRA Experience\n\nA big reason for this is keeping JIRA thriving as the best development tool around - and attracting all new customers.\n\nThe marketplace has already been a big success for plugin developers, and with JIRA 6 we expect even more customers to flock to JIRA’s new experience. So buckle up, and get ready for the journey.\n\nAnd we’re doing this development in plugins! In-line edit and the new issue nav were both developed as plugins, as were issue collector and the new project administration screens.\n\n\n
  • There are APIs everywhere and they are getting simpler, more powerful.\n\nhttps://www.hipchat.com/docs/api\nhttps://confluence.atlassian.com/display/BITBUCKET/Using+the+bitbucket+REST+APIs\nhttps://developer.atlassian.com/display/STASHDEV/Stash+REST+APIs\n\nHighlight Stash, how excited we are about it, and the 2 Codegeist winners.\n\nBamboo tasks... good ecosystem (press release about Dreamforce and Heroku enterprise and power of tasks)\n
  • There are APIs everywhere and they are getting simpler, more powerful.\n\nhttps://www.hipchat.com/docs/api\nhttps://confluence.atlassian.com/display/BITBUCKET/Using+the+bitbucket+REST+APIs\nhttps://developer.atlassian.com/display/STASHDEV/Stash+REST+APIs\n\nHighlight Stash, how excited we are about it, and the 2 Codegeist winners.\n\nBamboo tasks... good ecosystem (press release about Dreamforce and Heroku enterprise and power of tasks)\n
  • There are APIs everywhere and they are getting simpler, more powerful.\n\nhttps://www.hipchat.com/docs/api\nhttps://confluence.atlassian.com/display/BITBUCKET/Using+the+bitbucket+REST+APIs\nhttps://developer.atlassian.com/display/STASHDEV/Stash+REST+APIs\n\nHighlight Stash, how excited we are about it, and the 2 Codegeist winners.\n\nBamboo tasks... good ecosystem (press release about Dreamforce and Heroku enterprise and power of tasks)\n
  • There are APIs everywhere and they are getting simpler, more powerful.\n\nhttps://www.hipchat.com/docs/api\nhttps://confluence.atlassian.com/display/BITBUCKET/Using+the+bitbucket+REST+APIs\nhttps://developer.atlassian.com/display/STASHDEV/Stash+REST+APIs\n\nHighlight Stash, how excited we are about it, and the 2 Codegeist winners.\n\nBamboo tasks... good ecosystem (press release about Dreamforce and Heroku enterprise and power of tasks)\n
  • \n
  • This time last year we released two great features on top of the SDK that focused on improving development productivity. The first one is called FastDev.\n\nHow many of you here use FastDev?\n\nFor those that don’t, FastDev will compile your code for you simply by you refreshing your browser.\n
  • We also introduced the plugin module generator which made it easy to generate boilerplate code for your plugin.\n\nBoth of these features added heaps to the plugin development experience.\n
  • Almost immediately after AtlasCamp, we released the REST API Browser and the Developer Toolbox, which bundled together some other useful development tools.\n\n\n
  • Earlier this Summer, we took a step back to look at how new developers got started with Atlassian plugin development. It was a bit of an eye opener. For starters, installing our SDK is a big task for many developers. Depending on the OS, you might have to alter your environment variables, install the JDK, etc. All told, our documentation on how to install the SDK was very revealing.\n\nSo, we decided to fix this problem by creating a set of installers. We now have an installer for Windows, Mac, and Linux. And on Linux, you have the choice of installing DEB or RPM files or registering our DEB or RPM repository so you can just `apt-get install` or `yum install` the SDK. For mac users, you can still use the Homebrew recipe if you wish.\n\nOur goal here is to ease the pain of getting started. We realize this may not be a big deal for all of you who already have the SDK installed and are familiar with how to set it up.\n
  • Earlier this Summer, we took a step back to look at how new developers got started with Atlassian plugin development. It was a bit of an eye opener. For starters, installing our SDK is a big task for many developers. Depending on the OS, you might have to alter your environment variables, install the JDK, etc. All told, our documentation on how to install the SDK was very revealing.\n\nSo, we decided to fix this problem by creating a set of installers. We now have an installer for Windows, Mac, and Linux. And on Linux, you have the choice of installing DEB or RPM files or registering our DEB or RPM repository so you can just `apt-get install` or `yum install` the SDK. For mac users, you can still use the Homebrew recipe if you wish.\n\nOur goal here is to ease the pain of getting started. We realize this may not be a big deal for all of you who already have the SDK installed and are familiar with how to set it up.\n
  • ...and best of all it auto-upgrades now. Built into the SDK and run once a day before atlas-run or atlas-debug is a version check and it will upgrade if a new version if found. You’ll never be behind again!\n
  • The developer toolbar provides easy access to all the tools you need when developing addons. In place documentation, API brower, live refresh, and more.\n
  • The developer toolbar provides easy access to all the tools you need when developing addons. In place documentation, API brower, live refresh, and more.\n
  • Best thing of all.\nBut here’s a small preview of Live Reload... Basically, Live Reload is just that... real-time feedback as you code. Inspired by http://livereload.com/ which is a combination desktop app and browser extension that watches for file changes and auto-updates the browser page, and in the case of CSS, it doesn't even require a browser refresh!\n\nWe took their open-source javascript file, ditched the app and the browser extension and added that functionality into the fastdev plugin.\n\nThe Result? Live Reload can now be enabled for reloading plugin resources from the sdk. No desktop app. No browser extension. Just magic and a few pixies had to be sacrificed.\nIt currently supports live reloading the following file types: CSS, JS, LESS, VM, FTL, HTM / HTML, SOY, PNG, JPG, GIF!\n\nJonathan will have more to show tomorrow, but hopefully, I’ve gotten you pretty excited.\n
  • Best thing of all.\nBut here’s a small preview of Live Reload... Basically, Live Reload is just that... real-time feedback as you code. Inspired by http://livereload.com/ which is a combination desktop app and browser extension that watches for file changes and auto-updates the browser page, and in the case of CSS, it doesn't even require a browser refresh!\n\nWe took their open-source javascript file, ditched the app and the browser extension and added that functionality into the fastdev plugin.\n\nThe Result? Live Reload can now be enabled for reloading plugin resources from the sdk. No desktop app. No browser extension. Just magic and a few pixies had to be sacrificed.\nIt currently supports live reloading the following file types: CSS, JS, LESS, VM, FTL, HTM / HTML, SOY, PNG, JPG, GIF!\n\nJonathan will have more to show tomorrow, but hopefully, I’ve gotten you pretty excited.\n
  • \n
  • It’s been 3 months since the launch at Summit and when we first thought about launching the marketplace we had three main goals. \n
  • The first is goal of the marketplace was to increase the brillance of addons our customers can use - this means growing their quality, quantity, and continued support.\n
  • Well guess what... we currently have 112 Marketplace enabled addons! \n\nTo put this number in context and how awesome it actually is, we had 59 in June when we launched. This means we almost doubled in 3 months! And many of the new addons are brand new to Atlassian! \n\nThis has completely surpased our initial expectations!\n\nSource: Marketplace Stats Dashboard\n
  • The second goal was to remove the barriers for our customers to discover and purchase addons. There were many obvious barriers that we had to tackle first, such as like licensing, taxes, renewals, and evaluations. All these required a lot of grunt work in the UPM, the creation of the new Marketplace, legal, terms of use, and integration into our internal systems.\n\nBut... this is just the beginning. What is even more exciting is what this foundation is going to enable and i’d like to share what’s going to be shipping next that will remove even more friction and get your addons.\n
  • The problem is that most end-users will not randomly browse to the UPM and as a result they aren’t exposed to the wealth of addons that are available and can make their days more productive.\n\nWe want to use the marketplace to help you reach not just your admins but the end users, and effectively turn them into your fans.\n\nSo how can we do this? First, we will start embedding links to the marketplace in key areas of the products so that end users can discover addons related to the specific areas in the product (eg, custom fields or gadgets in JIRA as another example)\n
  • The problem is that most end-users will not randomly browse to the UPM and as a result they aren’t exposed to the wealth of addons that are available and can make their days more productive.\n\nWe want to use the marketplace to help you reach not just your admins but the end users, and effectively turn them into your fans.\n\nSo how can we do this? First, we will start embedding links to the marketplace in key areas of the products so that end users can discover addons related to the specific areas in the product (eg, custom fields or gadgets in JIRA as another example)\n
  • Clicking on the link will show an end-user view of UPM... with a big call to action. “Request” ab addon! Yes, we’ve now engaged our end users directly.\n
  • To make the administrators life easier, please provide a really compeling reason!\n
  • Now switching over to the administrators view of UPM - you can see what your users have been asking for, with business justification and a rolled-up total number of requests.\n\nThis hasn’t shipped just yet, \n\nAs you can We are really excited about the possibility that the continued removal of friction can provide for our teams.\n
  • The third goal was to ensure you have a thriving business that would allow you to continue to focus on providing great products for our customers.\n
  • Total gross dollars has surpased our forecasts, we have more addons, and more customers are evaluating and purchasing. The efforts to remove friction, although still very early, appear to be on the right track.\n\nSource: Marketplace Stats Dashboard\n
  • Total gross growth since launch.\n
  • We promised you this at Summit, and we’re delivering today. Launching now, vendors can now get daily reports of your actual _sales_, including Renewals, Upgrades, Experts’ Discounts and Refunds. You’ll know exactly what’s happening in your business on a daily basis.\n\nYou can evaluate if your marketing campains, promotions, or features are making a direct difference to your customers.\n\nhttps://developer.atlassian.com/display/MARKETFAQ/Systems+and+Reporting+Provided+for+Paid-via-Atlassian+Listings\n\n<>\n
  • We are building the marketplace to be the #1 enterprise marketplace in the world. \n\nBy building on this solid foundation, that you have supported and invested in, we are bullish about the massive opportunities it has opened up for us and our customers. Again, it’s still early but we are really excited about the future.\n\nWe have two great talks this week related to the marketplace:\n\n* Dave’s talk called “sell, sell, sell” provides numerous learnings on best practices for getting the most out of your addon marketing\n\n* Daniel’s lighting talk will promote some of the untapped opportunities that we see are available for vendors to take advantage of.\n
  • Although we have a great platform and plugin system, the growth potential of hosted is going to require a parallel evolution of how we allow people to extend and build on our products. \n\nWe are working on some new technology that I’d like to share with you today.\n
  • First, it’s important to understand that we still have over 80% of our gross sales coming from on premise licenses (eg, BTF) and it’s growing. The marketplace today gives you access to all those customers. It’s still our most important customer base. However, our hosted products are also growing, although still a much smaller portion of our business.\n\nThe opportunity we have is to leverage both the growing BTF and Hosted customers together. \n\n<>\n\nBut our current in-process plugin framework isn’t going to work in a large scale hosted environment in which products are being upgraded daily and where security and performance are hugely important. \n\nToday, I’m announcing plugins 3... the evolution plugins 2 for the cloud!\n
  • First, it’s important to understand that we still have over 80% of our gross sales coming from on premise licenses (eg, BTF) and it’s growing. The marketplace today gives you access to all those customers. It’s still our most important customer base. However, our hosted products are also growing, although still a much smaller portion of our business.\n\nThe opportunity we have is to leverage both the growing BTF and Hosted customers together. \n\n<>\n\nBut our current in-process plugin framework isn’t going to work in a large scale hosted environment in which products are being upgraded daily and where security and performance are hugely important. \n\nToday, I’m announcing plugins 3... the evolution plugins 2 for the cloud!\n
  • First, it’s important to understand that we still have over 80% of our gross sales coming from on premise licenses (eg, BTF) and it’s growing. The marketplace today gives you access to all those customers. It’s still our most important customer base. However, our hosted products are also growing, although still a much smaller portion of our business.\n\nThe opportunity we have is to leverage both the growing BTF and Hosted customers together. \n\n<>\n\nBut our current in-process plugin framework isn’t going to work in a large scale hosted environment in which products are being upgraded daily and where security and performance are hugely important. \n\nToday, I’m announcing plugins 3... the evolution plugins 2 for the cloud!\n
  • We’ve listened to feedback from our prototyping of “remote apps” and are building p3. Think of plugins3 as the evolution of what we used to code-name “remote apps” and it’s built around 4 core concepts:\n\nOnDemand and OnPremise (single source) - write once and run everywhere.\nUpgradability - stability, decoupling (both vendor and Atlassian going fast).\nNo more bundling into products - integration into the marketplace and you control deployment and upgrade timelines.\nMultiple languages (write in Java, Javascript, CoffeeScript...), this is really exciting and will make it more accessible for you to find great devs and also the dev cycle in javascript for example is a lot faster. No Maven. No build.\n\nBut there is more to p3 and cloud than just a technical challenge. It’s a new business environment, running a service 24/7 instead of throwing a JAR file to your customers. This will be a transformation for many of you that we will help you with.\n\nWhen p3 is released it will be backwards compatible with p2 plugins and continue to run plugins in OnPremisse.\n\n
  • We’ve listened to feedback from our prototyping of “remote apps” and are building p3. Think of plugins3 as the evolution of what we used to code-name “remote apps” and it’s built around 4 core concepts:\n\nOnDemand and OnPremise (single source) - write once and run everywhere.\nUpgradability - stability, decoupling (both vendor and Atlassian going fast).\nNo more bundling into products - integration into the marketplace and you control deployment and upgrade timelines.\nMultiple languages (write in Java, Javascript, CoffeeScript...), this is really exciting and will make it more accessible for you to find great devs and also the dev cycle in javascript for example is a lot faster. No Maven. No build.\n\nBut there is more to p3 and cloud than just a technical challenge. It’s a new business environment, running a service 24/7 instead of throwing a JAR file to your customers. This will be a transformation for many of you that we will help you with.\n\nWhen p3 is released it will be backwards compatible with p2 plugins and continue to run plugins in OnPremisse.\n\n
  • We’ve listened to feedback from our prototyping of “remote apps” and are building p3. Think of plugins3 as the evolution of what we used to code-name “remote apps” and it’s built around 4 core concepts:\n\nOnDemand and OnPremise (single source) - write once and run everywhere.\nUpgradability - stability, decoupling (both vendor and Atlassian going fast).\nNo more bundling into products - integration into the marketplace and you control deployment and upgrade timelines.\nMultiple languages (write in Java, Javascript, CoffeeScript...), this is really exciting and will make it more accessible for you to find great devs and also the dev cycle in javascript for example is a lot faster. No Maven. No build.\n\nBut there is more to p3 and cloud than just a technical challenge. It’s a new business environment, running a service 24/7 instead of throwing a JAR file to your customers. This will be a transformation for many of you that we will help you with.\n\nWhen p3 is released it will be backwards compatible with p2 plugins and continue to run plugins in OnPremisse.\n\n
  • We’ve listened to feedback from our prototyping of “remote apps” and are building p3. Think of plugins3 as the evolution of what we used to code-name “remote apps” and it’s built around 4 core concepts:\n\nOnDemand and OnPremise (single source) - write once and run everywhere.\nUpgradability - stability, decoupling (both vendor and Atlassian going fast).\nNo more bundling into products - integration into the marketplace and you control deployment and upgrade timelines.\nMultiple languages (write in Java, Javascript, CoffeeScript...), this is really exciting and will make it more accessible for you to find great devs and also the dev cycle in javascript for example is a lot faster. No Maven. No build.\n\nBut there is more to p3 and cloud than just a technical challenge. It’s a new business environment, running a service 24/7 instead of throwing a JAR file to your customers. This will be a transformation for many of you that we will help you with.\n\nWhen p3 is released it will be backwards compatible with p2 plugins and continue to run plugins in OnPremisse.\n\n
  • We are announcing p3 today. We will continue to be working with you over the next couple of months\n
  • Yon and Don are both are here - please don't hesitate to ask them any questions, express concerns or just share thoughts you may have. Don is giving a talk on p3 and will show off an example p3 addon and explain in a lot more detail the technical approach we are taking with p3.\n
  • Ecosystem: support is available and addons are getting better technically and getting better at UX and marketing.\n\nProducts: We are continuing make the user experience kickass and there are tons of new features to hack.\n\nThe SDK: Never update the sdk or refresh your brower again!\n\nMarketplace: It’s growing faster than we had imagined and there are still so many untapped opportunities.\n\nThe future: BTF is still big, but we are working on the future with p3.\n
  • Find the guys that will help you solve your problem and if you can’t, find me or Jonathan Nolan and we will find them for you.\n
  • Find the guys that will help you solve your problem and if you can’t, find me or Jonathan Nolan and we will find them for you.\n

AtlasCamp US 2012 Keynote, Jean-Michel Lemieux AtlasCamp US 2012 Keynote, Jean-Michel Lemieux Presentation Transcript

  • KeynoteJean-Michel LemieuxVP of Engineering
  • Text
  • Thanks
  • Thanks x2
  • About you Returning 42% First Camp 58%
  • 1. Ecosystem News2. Product News3. The SDK4. Marketplace
  • 1. Ecosystem News
  • 33Major Releases234Total Releases
  • 33Major Releases234Total Releases
  • 45 3 6 94Days Categories Prizes Entries
  • 45 3 6 94Days Categories Prizes Entries 43%
  • Dev Support
  • Dev Support 350Development Qs a month
  • Dev Support 350Development Qs a month
  • 2. Product News
  • User experienceTODO: picture??
  • simple & single line help and adminplugin points navigation
  • plugin pointssame experienceonpremise andondemand
  • developer.atlassian.com/design
  • AUI5.0
  • AUI • Toolkit for the design guidelines5.0 • Soy Templates • Flat Pack
  • AUI • Toolkit for the design guidelines5.0 • Soy Templates • Flat Packdeveloper.atlassian.com/display/AUI
  • TimelineOctober Dec (betas) February Header in OnPremise OnDemand Header, AUI and Bitbucket 5.0 default, and Styling
  • Confluence
  • Workbox NotificationsWorkbox TasksConfluence Mobile
  • Hacking Taskshttp://bitbucket.org/samtardif/workbox-cli
  • Hacking Notifications
  • Hacking Confluence MobileYour plugin here Your macro here
  • Confluence “Apps” Three Goals: • Show users what content they can create • Guide them in creating it (how) • Help them structure itThe “blank page” problem 32
  • Confluence “Apps” Three Goals: • Show users what content they can create • Guide them in creating it (how) • Help them structure it Why should you care?The “blank page” problem • Still in “concept” phase - help shape the solution! • Create add-ons which are first-class citizens of the content creation experience. 32
  • Confluence “Apps” Three Goals: • Show users what content they can create • Guide them in creating it (how) • Help them structure it Why should you care? Interested?The “blank page” problem sherif@atlassian.com • Still in “concept” phase - help shape the solution! • Create add-ons which are first-class citizens of the content creation experience. 32
  • 5.0 to 6.0
  • 5.0 and a lot in-between6.0
  • Two Streams 5.0 5.1 5.2 6.0Platform API, Integrations Perf, Scale Webhooks REST APIs Issue Links, StreamsUser Love Quick Edit Inline Edit and New Search and Search, Nav, and Issue Collector Issue Nav Design Refresh
  • Two Streams 5.0 5.1 5.2 6.0Platform API, Integrations Perf, Scale Webhooks REST APIs Issue Links, StreamsUser Love Quick Edit Inline Edit and New Search and Search, Nav, Issue Collector Issue Nav and Design Refresh
  • Am I Stable?
  • Am I Stable?
  • 5%Support Issues
  • 5%Support Issues 5Full-time SEs
  • 5%Support Issues 5Full-time SEs
  • 5%Support Issues 5Full-time SEs
  • Support Testing App App Build Project App Management Webhooks
  • Support Testing App App When a bug is fixed in JIRA, I want to automatically update a support ticket Build Project App Management Webhooks
  • Support Testing App When a bug is closed in App When a bug is fixed in JIRA, I want my test JIRA, I want to cases to reflect that fact automatically update a support ticket Build Project App Management Webhooks
  • Support Testing App When a bug is closed in App When a bug is fixed in JIRA, I want my test JIRA, I want to cases to reflect that fact automatically update a support ticket I would like to trigger a build when an issue Build finishes implementation Project App Management Webhooks
  • Support Testing App When a bug is closed in App When a bug is fixed in JIRA, I want my test JIRA, I want to cases to reflect that fact automatically update a support ticket I want to generate I would like to trigger a reports once a build when an issue milestone is Build finishes implementation complete Project App Management Webhooks
  • JIRA Webhooks Why • No plugin development required • Push instead of poll • Notification includes delta
  • JIRA Webhooks Why • No plugin development required • Push instead of poll • Notification includes delta What HTTP POST to the URL you designate with information on the event that occurred
  • JIRA Webhooks Why • No plugin development required • Push instead of poll • Notification includes delta What HTTP POST to the URL you designate with information on the event that occurred
  • What defines a webhook? Name: "The simplest webhook" Simple URL: http://www.myremoteapplication.com/webhookreceiver “Give me every issue event in JIRA”
  • What defines a webhook? Name: "The simplest webhook" Simple URL: http://www.myremoteapplication.com/webhookreceiver “Give me every issue event in JIRA” Name: "A more advanced webhook" Very URL: http://www.myremoteapplication.com/webhookreceiver Powerful! JQL: Project = JRA AND fixVersion IN ("5.1", "5.2") Events: issue_updated, issue_created “Limit the events and the issues I receive”
  • The Path to 6.0
  • The Path to 6.0
  • HipChatPushimportantevents to chatrooms
  • HipChat StashPush Workflow,important permissions, richestevents to chat and complete APIrooms
  • HipChat StashPush Workflow,important permissions, richestevents to chat and complete APIroomsBambooTasks,tasks,tasks, andtasks
  • HipChat StashPush Workflow,important permissions, richestevents to chat and complete APIroomsBamboo BitbucketTasks, Fetch code,tasks, analyse, reports,tasks, and and issuetasks integrations
  • 3. The SDK
  • 4.0
  • 4.0
  • 4. The Marketplace
  • 3Goal 52
  • BrilliantAdd-ons
  • 111Add-onsAvailable 54
  • RemoveBarriers to 55
  • 57
  • 57
  • 58
  • 59
  • ThrivingBusinesses 60
  • 1 Million$ Dollars 61
  • 60%MoM total $
  • $ Sales API for 63
  • Next... 64
  • 5. The Future of Addons
  • Highlights
  • Highlights Single Binary
  • Highlights In-process Remote calls Single Binary
  • Highlights In-process Remote calls Single Binary
  • Highlights In-process Remote calls Single Binary ...
  • When? Today March JuneAnnouncement! Beta 1. 0
  • Who? Where? Tech Lead Don Brown Google Group don@atlassian.com atlassian-remoteapps-dev Issues and Doc http://remoteapps.jira.com Product Manager Yon Golan yon@atlassian.com
  • Recap1. Ecosystem2. Products3. The SDK4. Marketplace
  • Getting the most of Camp!
  • Getting the most of Camp! 1:1 4:1 Sessions Atlassians