Recommended
More Related Content
What's hot
What's hot (20)
Similar to AUG NYC - Atlassian Server Updates
Similar to AUG NYC - Atlassian Server Updates (20)
More from AUGNYC
More from AUGNYC (18)
Recently uploaded
Recently uploaded (20)
AUG NYC - Atlassian Server Updates
- 1. AILEEN HORGAN | SERVER SW TEAMS GTM Atlassian Server Updates What’s New + Roadmap Preview
- 2. The way teams work is changing
- 3. Best practices to enable modern teamwork Agile Plan, prioritize and iterate quickly based on changing priorities DevOps Improve release cadences, MTTR and spend less time on unplanned work ITSM Deliver the best, customer-centric service management
- 5. Make investments that amplify teamwork at scale SERVER & DATA CENTER
- 6. JAC & Community Open forums for feedback, discussion and feature requests Atlassian Teams Support, Premier Support, and TAMs Customer Research Surveys, interviews, user research studies Market Trends What is the future of teamwork? Inputs for Development
- 7. shipped Jira Software votes from jira.atlassian.com
- 9. RECENT RELEASES Jira Software 7.4 Jira Software 7.5 Jira Software 7.6 JUNE 2017 SEPTEMBER 2017 NOVEMBER 2017 Priorities per project JMX monitoring Data Center performance Project level admin Kanban backlog Issue export Azure deployment Split issues Subtasks in backlog Sprint goals
- 10. “KANPLAN” Backlog view Get the structure of scrum with the fluidity of Kanban. Subtasks Please watch the tutorial to learn how to create call-outs on screenshots in this template.
- 11. PRIORITIES PER PROJECT More clarity Assign the right priority to tasks in your projects. Greater flexibility To create different priority types depending on the team. Admin power No longer need to restrict creation of new priority types.
- 12. RICH TEXT EDITOR IMPROVEMENTS Addressing feedback We’ll close out common requests and bugs Image handling Pasting images will be hassle- free Switching modes Flip between rich text and text mode without losing formatting Please remember You don’t always need the line or text at all.
- 13. r Ultimate search Quickly find what you’re looking for, not only issues.
- 14. Improved notifications Reduce Jira Software email chattiness. Top-requested features Shared filters & dashboards Let teams move faster and share best practices. Mail server configuration Making it easier to set up and troubleshoot mail issues.
- 15. Archiving Performance improvements and decluttered projects and boards. Tools for trimming unused issues and projects from Jira instances. EXPLORATION PHASE
- 16. Jira Mobile Apps Enable teamwork anywhere with Jira Following Confluence mobile apps: stay tuned for updates and what to expect EXPLORATION PHASE
- 17. 6 Weeks Faster and more predictable release cadence, consistently delivering value 12 Weeks Variable time between releases, longer to deliver features
- 18. Enterprise releases Once a year, we will certify a release with back-ported bug fixes for enterprise customers to upgrade to.
- 20. RECENT RELEASES Confluence 6.3 Confluence 6.4 Confluence 6.5 JULY 2017 SEPTEMBER 2017 NOVEMBER 2017 Azure deployment Improved email threading Stability: collab editors limit Attachment indexing More DBs Recently “worked on” & drafts Performance testing framework
- 22. Smart Mentions @mentioning gets smarter and faster. Improved Search Early stages. Goal: make it easier and simpler for users to find content Looking ahead…
- 24. PORTFOLIO FOR JIRA Data-driven roadmaps Visibility into projects & teams Seamless integration with Jira Software
- 27. API Push and pull data from Portfolio. Potentially improve capacity planning Simpler planning Create a light-weight roadmap that you can share with your teams Key investments
- 29. DevOps A culture where dev and ops collaborate to build a faster, more reliable release pipeline.
- 31. One project, one… Space Project Project Project Admin by… Space Project Repository Plan Room Room
- 32. NEW IN 5.2 One project, one… Room Space Project Project Project Admin by… Room Space Project Project Project NEW IN 6.2
- 33. BETTER TOGETHER - BAMBOO AND BITBUCKET Bamboo Specs for Bitbucket • Bamboo now reacts automatically to CI/CD config code stored in Bitbucket Server
- 34. Jenkins support Trigger builds automatically and view results inside of Bitbucket - no add-on needed PLA 2.0 Comply with regulatory requirements with minimal administrative overhead Code insights Reveal security vulnerabilities, code coverage, and test results in Bitbucket Bitbucket
- 35. Jenkins support Trigger builds automatically and view results inside of Bitbucket - no add-on needed PLA 2.0 Comply with regulatory requirements with minimal administrative overhead Code insights Reveal security vulnerabilities, code coverage, and test results in Bitbucket Bitbucket
- 36. Jenkins support Trigger builds automatically and view results inside of Bitbucket - no add-on needed PLA 2.0 Comply with regulatory requirements with minimal administrative overhead Code insights Reveal security vulnerabilities, code coverage, and test results in Bitbucket Bitbucket
- 37. YAML Bamboo YAML for Bitbucket Server Docker Pipelines Run builds and deployment projects inside Docker containers fully controlled by end users. Bamboo New agent tiers Up to 1000 agents with a single server
- 38. YAML Bamboo YAML for Bitbucket Server Docker Pipelines Run builds and deployment projects inside Docker containers fully controlled by end users. Bamboo New agent tiers Up to 1000 agents with a single server
- 39. YAML Bamboo YAML for Bitbucket Server Docker Pipelines Run builds and deployment projects inside Docker containers fully controlled by end users. New agent tiers Up to 1000 agents with a single server Bamboo
- 41. General Availability Launched Hipchat Data Center in June 2017 Beta Mobile and improved notifications Recently Released
- 42. Hipchat as an application Exploration phase. Greater flexibility and control for how you deploy Hipchat (+add’l DB support) Jira integrations Stronger integrations to improve your DevOps workflow and move faster . New mobile & desktop apps Refreshed look and feel with a simpler login experience. Hipchat
- 43. Hipchat Hipchat as an application Exploration phase. Greater flexibility and control for how you deploy Hipchat (+add’l DB support) Jira integrations Stronger integrations to improve your DevOps workflow and move faster . New mobile & desktop apps Refreshed look and feel with a simpler login experience.
- 44. Hipchat Hipchat as an application Exploration phase. Greater flexibility and control for how you deploy Hipchat (+add’l DB support) Jira integrations Stronger integrations to improve your DevOps workflow and move faster New mobile & desktop apps Refreshed look and feel with a simpler login experience.
- 47. RECENT RELEASES JSD 3.7 JSD 3.8 JSD 3.9 JULY 2017 SEPTEMBER 2017 NOVEMBER 2017 Canned responses improvements Automated approvals Live monitoring with JMXCanned responses SLA copy configuration
- 48. Advanced & automated approvals Visibility & notifications improvements to make ‘change approvals’ intuitive and actionable. Auto approve based on preset conditions. Azure support Deployment flexibility for Jira Service Desk Data Center Priorities per project Priorities that are purpose built for and by different team workflows Change Management
- 49. Advanced & automated approvals Visibility & notifications improvements to make ‘change approvals’ intuitive and actionable. Auto approve based on preset conditions. Azure support Deployment flexibility for Jira Service Desk Data Center Priorities per project Priorities that are purpose built for and by different team workflows Change Management
- 50. Advanced & automated approvals Visibility & notifications improvements to make ‘change approvals’ intuitive and actionable. Auto approve based on preset conditions. Azure support Deployment flexibility for Jira Service Desk Data Center Priorities per project Priorities that are purpose built for and by different team workflows Change Management
- 53. SSO Provides SSO across Atlassian server products Crowd Data Center Cluster Host on a cluster of servers Integrate with LDAP Connect to one or multiple user directories
- 54. We will prioritize differently across our deployment options SERVER, DATA CENTER, AND CLOUD
- 56. Thank you
Editor's Notes
- My name’s Aileen and I’ve been with Atlassian for a little over 4 years and today I’m going to share a bit about what the Server organization has been up to. i’ll provide a quick look back at what we’ve recently shipped and give you a preview of what’s to come
- In working with 10s of thousands of organizations worldwide, we see that the way teams work is changing dramatically. This probably feels obvious but the way the previous generations worked doesn’t hold up in our modern lives You can call this a “digital transformation” but essentially, team work has changed
- We see this as a result of three primary factors: Workforce is in multiple locations and often in multiple timezones The pace of innovation is increasing, competitive pressure is increasing, customers want more all the time - more products, more service. There’s a shift in thinking about employees first - to engage and retain them. From a teamwork perspective, this means companies have to ensure employees stay engaged and can identify with their work and their teams while being distributed and coping with demands in an increasingly faster-paced work environment. [IF YOU WANT TO ELABORATE, BELOW ARE MORE NOTES ON EACH FACTOR] Let’s quickly go over each of these factors: In a 2016 survey among our customer base, we found that 72% said some portion of their team works in a different location. source: Atlassian 2016 software development trends survey / report So from a teamwork perspective you have to account for distributed teams Innovation And, the pace of innovation in all your businesses is changing rapidly. Customers are expecting more: always-on customer service, newer products - be it cars or software, lower prices or higher quality. Your competitors and you are in a race to deliver this. From a teamwork perspective this means that you have to account for a team with an always-on culture, and need to collaborate fast all the time to meet customer demands and competitive pressure. The third factor is an increased focus on employee satisfaction and retention this is 3 things - a war for talent, because statistics show that people stay at jobs for 4-5yrs. What do companies have to do to attract and retain them? Companies are paying more attention to corporate culture and values like diversity and inclusion because employees demand this. Company structures are also evolving to keep employees engaged - towards more autonomous structures.
- To thrive and remain competitive, many of our customers are adopting best practices that enable modern teamwork. Specifically, methodologies like agile, DevOps and ITSM. From a Server perspective, this is how we approach our development investments. We’re focused on enabling these practices as scale. In addition to these focus areas, we also think about the Enterprise organization as a whole.
- and building for the enterprise… Atlassian has worked with over 5000 teams at large enterprises worldwide. They all face this issue of implementing tools for modern teamwork at large scales of 1000 employees and more. Providing enterprise features as we continue to look at how companies scale Photo by JOHN TOWNER on Unsplash
- I want to reinforce that you will see us prioritize differently across our different deployment options of Server, Cloud, and Data Center. This is a change from our one size fits all approach of the past. Our new approach gives us a lot more flexibility to deliver your top priorities.
- And we turn to you (and the market) to help us prioritize our investment areas You told us on jira.atlassian.com that there's much more we can do to help your teams remain flexible at scale.
- We have listened carefully and in the most recent Jira releases, we managed to ship features that you asked for and have closed tickets with more than 7,300 votes for Jira Software alone. We’ll continue to look to this site to ensure we’re addressing your top needs. Please keep the suggesting coming! Jira: PPP = 2,500 Kanplan = 570 + 1079 + 544 (epic support) PLA = 1525 deletion of sprints = 546 sprint goals = 269 split issue = 109 drag / drop subtasks = 223 … 3 thousands of your votes. Apart from what I’ve already mentioned this list also includes ability to rename and delete sprints or ability to drag&drop subtasks for more efficient planning.
- Let’s take a few minutes to look at the practice we’re likely best known for: agile. While many of our products map to agile practices, let’s dive into: ◦ JSW ◦ Portfolio for Jira ◦ Confluence
- More than 500 of you told us that working in Kanban would be much easier with a backlog We know development teams practicing agile often don’t fit into the strict category of either Scrum or Kanban. Teams practicing Kanban for the flexible planning and full transparency still want a place to plan and capture issues that are outside their scope of work. As a result, these teams use their to-do list as a makeshift backlog. This column can get lengthy, and as it grows it becomes impossible for users to see and organize issues on their board. Now teams working in kanban get a dedicated backlog view, allowing them to plan and prioritize with the structure of scrum, but move issues through development with the fluidity of kanban. This is one of the examples where we release and perfect a feature in our cloud products before bringing it over to Server. https://www.atlassian.com/blog/jira-software/jira-software-server-7-4
- After 13+ years and over 2,500 votes, we closed the #1 customer voted feature request in our public issue tracker, priorities schemes per project.
- Looking ahead…
- With quick search suggestions, [build] we want to make it easier for teams with growing number of tasks and projects to quickly find most relevant information.
- we’ll also continue to address some of our top-requested features like mail server configuration, better email notifications, and shared filters and dashboards
- Additionally, we know that many of our Enterprise customers face…
- The final note on Jira Software is our approach to amplifying our releases and getting fixes and features into your hands sooner. Our goal is to decrease our time to market; we’re aiming for a 6 week release cadence (currently shortening from 12 to ~8)
- Our release cadence for Jira Software is increasing, so you’re going to see more frequent releases for the product. Bitbucket is already quite frequent, every 5 weeks. But we know that our largest enterprise customers can’t keep up with this release cadence. So we need to back port fixes to a stable release so enterprise customers can upgrade AND get the benefit of increased quality. We’re proposing a shift to having specific Data Center releases designated as Enterprise releases. Our current thinking is that we will ship at least one Enterprise release a year. We will back port high impact bugs to any Enterprise releases for the two years after it’s initial release. These releases would also be the releases which would support Zero Downtime upgrades for Jira Software (you would be able to ZDU from one Enterprise release to another) Our initial focus here is JSW and Confluence but other products might be included later We’re presenting this to you, not as an announcement, but as a proposal to the customers who we want to benefit with this program. We’d love your feedback because you are main target for this program.
- Let’s take a look at what the Confluence Server team has been up to
- https://confluence.atlassian.com/doc/confluence-6-3-release-notes-909642701.html max limit on collaborative editors is 12 concurrent users When a file is uploaded in Confluence, its text is extracted and indexed so that people can search for the content of a file, not just the filename. This is a pretty memory hungry process, and has caused out of memory errors for some customers. This release has some big improvements to the safeguards that prevent out of memory errors in your site. Here's the basics: • If your uploaded file is 100 MB or more, Confluence will skip extracting content, and just index the filename. • If your uploaded file is Word, Excel, PDF or text, Confluence will only extract content up to a specific limit. • If the text extracted from the file is more than 1 MB, it will be searchable, but won't show as an excerpt in search results. support for PostgreSQL 9.6 and MySQL 5.7 databases. We also now support the latest MySQL, PostgreSQL and Oracle JDBC drivers. https://confluence.atlassian.com/doc/confluence-6-4-release-notes-934721238.html https://confluence.atlassian.com/doc/confluence-6-5-release-notes-938862614.html
- Mobile for Server - beta released with 6.5 (end of Nov) Access to information anytime, anywhere to drive tram collaboration
- The last product under the agile at scale theme is Portfolio for Jira. Scale agile across multiple teams Visibility across some of your largest and most complex projects
- Portfolio for JIRA is an agile PPM add-on which seamlessly integrates with JIRA software. It allows you visualize roadmaps across various work streams and manage dependencies using a comprehensive algorithm Every team can create their roadmap, make data driven decisions and keep everyone informed on status and progress.
- programs or a “plan of plans”- july (2.3) An aggregated view across all of your plans Programs give you a high-level view of your work, so you can efficiently keep track of the status and progress of your work items across multiple plans. https://www.atlassian.com/blog/announcements/scale-agile-practices-with-programs-in-portfolio-for-jira https://confluence.atlassian.com/jiraportfolioserver/programs-931037964.html
- We also recently delivered a dependency report You can use the dependencies report to see the dependencies (both scheduled and unscheduled) that the work items in your plan may have. This helps in mitigating any possible project delays, as well as facilitating risk management processes efficiently. https://confluence.atlassian.com/jiraportfolioserver/dependencies-report-935577893.html
- API Portfolio schedules work according to the available capacity. For customers with many teams updating these teams with: member names, skills, absences, availabilities is cumbersome especially for enterprises with many teams. Once you have an accurate and updated state of team capacity you can have a super realistic schedule which has lots of virtues such as identify bottlenecks in advance, etc.. Simpler planning Many customers report 'not understanding the scheduling algorithm’ The goal of a simpler plan is for any user to effortlessly create a roadmap that they can effortlessly share with stakeholders 'Clarity of calculation' was the second most major pain point from enterprise customers
- Alright, we just explored our primary agile applications, now let’s take a look at our investments in DevOps, which we see as an extension of agile practices
- There are many definitions of DevOps out there, but Atlassian defines it as - a culture where dev and ops collaborate to build a faster, more reliable release pipeline. I’m going to jump into some product updates but if your teams are starting implement DevOps, or want to check-in on your progress, I recommend taking a look at the Atlassian Team Playbook use case, or set of plays and recommended health monitor, to help considering a DevOps transformation think about how to align better This is also a great way for established DevOps teams to check-in on how well they’re connecting with one another.
- This is how project administration looked in different Atlassian products until recently. For any given project, administration for most products was done at an appropriately high level. But administration in Bitbucket Server and Bamboo involved managing more information down at the repository and plan level.
- Now, Bitbucket and Bamboo administration has a simpler and smaller set of settings available at the project level. Everyone can spend less time worrying about whether the team's workflow is consistent everywhere.
- We continue to invest heavily into Bitbucket Server and Bamboo integration. We recently released builds triggered by pull requests in Bitbucket. In Bamboo 6.0 we released Specs allowing builds to be defined as code. In Bamboo 6.2 we round out the Specs feature by tying it seamlessly into your Bitbucket workflow. Simply store your build definitions alongside your code, commit changes as you would for your feature work, and Bamboo will react automatically to changes. This puts the power and control of declarative builds right into developers’ hands.
- Bitbucket Server brings information about your flow to the forefront through Code Insights, revealing security vulnerabilities, code coverage, and test results directly in the user interface. With a deeper understanding of where your team stands, the ability to make improvements to flow becomes much more tangible.
- Continuous integration and automation is a key ingredient for practicing DevOps and can greatly impact flow. Whether you're using Bamboo, Jenkins, or both Bitbucket Server makes setting up build pipelines a painless and quick process sans the need for add-ons or webhooks. Builds can be triggered automatically against changes via pull requests or commits and their results easily accessible throughout the Bitbucket UI.
- Lastly, controlling your flow is just as important as improvement or visibility, which is why Bitbucket Server is introducing several enhancements to project level administration making complying with strict regulatory requirements easier with minimal administration overhead.
- Improvements to your build pipelines can have a huge impact to the speed of the "idea to production" flow. Bamboo specs as YAML, provides an alternative to the Java-based specs for users looking for a simplified way of using configuration as code.
- Another feat investment, Docker Pipelines, makes it very easy for users to define their build and deployment environments as Docker containers and run them. This saves a lot of unnecessary admin overhead and allows teams to create consistent and replicable environments as and when needed. This cane be done via UI or using Bamboo Specs.
- For large enterprise needs, new agent tiers at the 500 & 1000 level bring support for massive scale to your CI/CD flow. Organizations are no longer restrained by the size or scale of their build system.
- Focusing on the real-time communication throughout your DevOps practice, let’s take a look at what Hipchat has been up to
- We’re also focusing on improvements to migration experience from Server to DC Improved notifications = unread state (the ability to see notifications that you’ve missed)
- mobile and desktop apps are compatible for both server and data center
- Those were updates on more of the dev side of DevOps, let’s take a look at the IT / Ops side and what Jira Service Desk has been up to.
- • At Atlassian, we approach ITSM a little differently. We believe the ITSM mindset needs to shift, both culturally and in ways of working. We want to break down barriers and silos and increase collaboration, especially between dev and IT teams, so everyone has full visibility and is on the same page. • We’re focusing on ways to make IT teams more agile; to react quickly to changing needs and the demand to increase velocity when delivering new technology features and functions. The benefit of this is iterative process improvement with fast delivery and results. The team’s focus is relevant to current business needs rather than being guided by a long-term, “set in stone” project plan. • This also affects the identification and elimination of waste to make IT teams more efficient. How can we remove steps slowing down the ability to deliver? Are there a series of “gates” to pass through to progress in a serial-based activity flow rather than a more lean and agile based approach where only truly necessary steps are followed?
- Canned responses allow you to create, edit, and manage responses that can be used at any time directly from the view issue screen. SLA copy config: project administrators can now copy over SLA configurations from existing projects with just a few clicks. It’s as easy as choosing the project you want to copy the configurations from and importing them. https://www.atlassian.com/blog/it-teams/get-time-back-canned-responses-sla-copy-configurations-jira-service-desk-server 3.9: Add issue key and personalization to canned responses Implemented a THEN clause which allows you to automatically approve or decline requests when they meet certain criteria. We’ve also introduced live monitoring with JMX to help you make better decisions about how to maintain and optimize machine resources. JMX lets you monitor your Jira instance in real time using objects called MBeans to expose data and resources about your application. https://www.atlassian.com/blog/jira-service-desk/more-power-and-control-in-jira-service-desk-server-3-9
- Looking ahead, the team will be focusing on richer capabilities in Change management When it comes ITSM change management, we’re certified for change management out of the box. But we’re scratching the surface from an enterprise perspective. We are committed to deeper capabilities in those areas. • Automated approvals - Ability to auto approve based on preset conditions.
- • Azure for DC - Flexible deployment with Azure for JSD DC
- Bringing learnings from Jira Software’s priorities per project into Jira Service Desk
- Shifting gears to look at how all teams access atlassian applications… Since 2007, Crowd has been helping Atlassian’s self-hosted customers meet their identity management needs. Crowd allows you to easily centralize user management for all of your Atlassian products and avoid mistakes without losing the confidentiality of your data. On top of simplifying the lives of administrators, Crowd makes life easy for your team. With single sign-on, teams can log into one application they need access to and then be able to switch applications without having to provide a username and password again.
- In August, we introduced Crowd Data Center, identity management built for HA
- Integrates with your existing identity infrastructure, including Microsoft Azure AD!
- In closing, I want to reinforce our commitment to our Server customer base. We will continue to prioritize differently across our deployment options to address the unique needs of our customers. Our new approach gives us a lot more flexibility to deliver your top priorities.
- Please continue to share your feedback with us, we’re listening.