Embed Size (px)
Citation preview
Confluence Connect is prime time
KATE WEST-WALKER DEVELOPER • @KAPWW
BEN MACKIE PLATFORM GUY • @BDMACKIE
KATE WEST-WALKER • DEVELOPERBEN MACKIE • PLATFORM GUY
Confluence is
One place for your TEAM to get the job done together
Confluence helps teams get the job done
PROJECT COLLAB REFERENCE DOCS TEAM KNOWLEDGE
Confluence helps teams get the job done
PROJECT COLLAB REFERENCE DOCS TEAM KNOWLEDGE
Theme 1: Support Team Jobs in the Cloud
PROJECT COLLAB REFERENCE DOCS TEAM KNOWLEDGE
Theme 2: Enable Cloud opportunities
Service Integrations
Extensions at Scale
Our focus
Patterns Reusable approaches to extending Confluence
Our focus
Adoption Discovery, engagement and
quality standards
Growth Enabling new add-ons and scaling with a new
dev experience
Patterns Reusable approaches to extending Confluence
I N T E G R AT I O N PAT T E R N S
C R E AT I O N PAT T E R N S
Agenda
R O A D TO L A U N C H !
W O R K I N P R O G R E S S
D E V E X P E R I E N C E
C O N F L U E N C E A P I
Confluence
Confluence API
Content history and drafts
Blueprints and templates
Metadata
Expansions
Manage
Confluence API
CQL
Extensibility
Search
Manage
Confluence API
Webhooks
JavaScript APIs
Interact
Search
Manage
C R E AT I O N PAT T E R N S
C O N F L U E N C E A P I
Agenda
R O A D TO L A U N C H !
W O R K I N P R O G R E S S
D E V E X P E R I E N C E
I N T E G R AT I O N PAT T E R N S
API
Macros
Patterns
Macros
Integrations
What can I build with macros?
Specialised Content
Composed Content
Macros
Viewing EditingCreating
Default editor
Custom editor
Full screen designer
Property panel
Inline iframe Insert menu
Autoconvert
Macros
API
Macros Page extensions
Patterns
Extend the action zone for your page action
Extend the action zone for your page action
Add page actions to the menu
I T E M 2
I T E M 1
I T E M 3
I T E M 4
Agenda
I T E M 2
I T E M 1
I T E M 3
I T E M 4
Agenda
Extend the byline to see context at a glance
I T E M 2
I T E M 1
I T E M 3
I T E M 4
Agenda
Extend the byline to express page status
Page extensions
API
Macros Page extensions Search extensions
Patterns
Alias your Content Properties…
…filter on them with CQL
category = ‘demonstration’
Search extensions
Search extensions
Integrating content properties with UX
Extend search filters with metadata managed by your add-on
API
Integrate
Macros Page extensions Search extensions
Patterns
I N T E G R AT I O N PAT T E R N S
C O N F L U E N C E A P I
Agenda
R O A D TO L A U N C H !
W O R K I N P R O G R E S S
D E V E X P E R I E N C E
C R E AT I O N PAT T E R N S
API
Integrate
Create
Macros Page extensions Search extensions
Blueprints
Patterns
Automate consistent page creation within
your team
Blueprints 2.0
Use multi-page blueprints to create groups of
related pages instantly
Create page templates with custom content
from your add-on
$var
Blueprints
API
Integrate
Create
Macros
Custom content
Page extensions Search extensions
Blueprints
Patterns
Custom content
DIAGRAM
ATTACHMENTS
Page
QUESTION
ANSWER
COMMENT
Space
Custom content
DIAGRAM
ATTACHMENTS
Page
QUESTION
ANSWER
COMMENT
Space
Custom content
DIAGRAM
ATTACHMENTS
Page
QUESTION
ANSWER
COMMENT
Space
Custom content
Custom content
Custom content
DIAGRAM
ATTACHMENTS
PageDefine your custom
content view
Custom content
Integrate with navigation and
search
Custom content
Integrate with navigation and
search
Content property:
ac:custom-content:search-body
Custom content
Custom content supports existing and new jobs
Custom Content Steve Lancashire
Wed 3:35 PM
PROJECT COLLAB REFERENCE DOCS TEAM KNOWLEDGE NEW JOBS
I N T E G R AT I O N PAT T E R N S
C O N F L U E N C E A P I
C R E AT I O N PAT T E R N S
Agenda
R O A D TO L A U N C H !
W O R K I N P R O G R E S S
D E V E X P E R I E N C E
Getting started Matthew Jensen
Wed 2:45 PM
Design guidelines
UX Guidelines Brian Swift
Tue 4:05 PM
I N T E G R AT I O N PAT T E R N S
C O N F L U E N C E A P I
C R E AT I O N PAT T E R N S
D E V E X P E R I E N C E
Agenda
W O R K I N P R O G R E S S
R O A D TO L A U N C H !
IntroductionThe goal of this marketing plan is to outline the strategies, tactics, and programs that will make the sales goals outlined in the fashion business plan a reality in the year 2015.
Maintenance is not about banging out as many fixes as you can in 2 weeks. There are several valid reasons for including someone who isn't on maintenance.
ObjectivesHave a plan and budget for FY2013 accounting for growth and marketing activites for the coming year.
Phase 1Warranty fix. If a team has pushed out their brand new feature and it's misbehaving then it's their responsibility to fix it. Don't just assign the ticket to them and call it a day. Contact the team (in person or via HipChat), explain what you're seeing, ensure that fixing the bug is the responsible team's highest priority.
The NFI condition. It's not uncommon to encounter an issue where you have no idea where to start. Again, don't give up and assign it to someone senior! This is your chance to learn! Pair with someone who does know where to start and soak as much information from them as possible.
Phase 2Maintenance doesn't stop when the bug is fixed
When you're fixing something, ask yourself; how did this happen? Individuals make mistakes, but for a bug to make it to production means something in our process failed. Was there a QA involved in the development? How's the test coverage? Is there something in the codebase that is inherently confusing and often gets misused by devs?
Record the answers to this down somewhere, at the end of a maintenance stint you'll need to recall these details to share with the rest of the team.
Some of the problems you get will be really difficult. Getting a knowledgable teammate involved in debugging can often help you find the root cause for something quicker. I'm a serial rabbit hole explorer; pairing with someone stops me from wasting time on something unrelated.
Never forget that the bug you're fixing affects customers. Fixing their issue is a great start, but great communication with customers can really make a difference. Irate customers can be placated by a quick update on their issue; silence will only lead to more anger. The advocates are more than happy to help you with this.
In some cases fixing the bug isn't enough; be conscious of the pain the customer has felt. Often something small like a free month of OnDemand can help them forget about that time we almost deactivated their account.
Many of us are on teams dedicated to certain parts of our system landscape. Maintenance is your chance to branch out, learn things, and become a better developer.
Marketing Home
Marketing home
Pages
Blog
Questions
Calendar
?
SPACE SHORTCUTS
CHILD PAGES
Space Administration
Marketing
Marketing Strategy CY…
Weekly Reports
Campaigns
Marketing Home
Campaign planning Fy16
IntroductionThe goal of this marketing plan is to outline the strategies, tactics, and programs that will make the sales goals outlined in the fashion business plan a reality in the year 2015.
Maintenance is not about banging out as many fixes as you can in 2 weeks. There are several valid reasons for including someone who isn't on maintenance.
ObjectivesHave a plan and budget for FY2013 accounting for growth and marketing activites for the coming year.
Phase 1Warranty fix. If a team has pushed out their brand new feature and it's misbehaving then it's their responsibility to fix it. Don't just assign the ticket to them and call it a day. Contact the team (in person or via HipChat), explain what you're seeing, ensure that fixing the bug is the responsible team's highest priority.
The NFI condition. It's not uncommon to encounter an issue where you have no idea where to start. Again, don't give up and assign it to someone senior! This is your chance to learn! Pair with someone who does know where to start and soak as much information from them as possible.
Phase 2Maintenance doesn't stop when the bug is fixed
When you're fixing something, ask yourself; how did this happen? Individuals make mistakes, but for a bug to make it to production means something in our process failed. Was there a QA involved in the development? How's the test coverage? Is there something in the codebase that is inherently confusing and often gets misused by devs?
Record the answers to this down somewhere, at the end of a maintenance stint you'll need to recall these details to share with the rest of the team.
Some of the problems you get will be really difficult. Getting a knowledgable teammate involved in debugging can often help you find the root cause for something quicker. I'm a serial rabbit hole explorer; pairing with someone stops me from wasting time on something unrelated.
Never forget that the bug you're fixing affects customers. Fixing their issue is a great start, but great communication with customers can really make a difference. Irate customers can be placated by a quick update on their issue; silence will only lead to more anger. The advocates are more than happy to help you with this.
In some cases fixing the bug isn't enough; be conscious of the pain the customer has felt. Often something small like a free month of OnDemand can help them forget about that time we almost deactivated their account.
Many of us are on teams dedicated to certain parts of our system landscape. Maintenance is your chance to branch out, learn things, and become a better developer.
Legal Home
Legal home
Pages
Blog
Questions
Calendar
?
SPACE SHORTCUTS
CHILD PAGES
Space Administration
Engineering Home
Engineering project plan
Engineering Teams
New starter guide
Decision log
Legal
IntroductionThe goal of this marketing plan is to outline the strategies, tactics, and programs that will make the sales goals outlined in the fashion business plan a reality in the year 2015.
Maintenance is not about banging out as many fixes as you can in 2 weeks. There are several valid reasons for including someone who isn't on maintenance.
ObjectivesHave a plan and budget for FY2013 accounting for growth and marketing activites for the coming year.
Phase 1Warranty fix. If a team has pushed out their brand new feature and it's misbehaving then it's their responsibility to fix it. Don't just assign the ticket to them and call it a day. Contact the team (in person or via HipChat), explain what you're seeing, ensure that fixing the bug is the responsible team's highest priority.
The NFI condition. It's not uncommon to encounter an issue where you have no idea where to start. Again, don't give up and assign it to someone senior! This is your chance to learn! Pair with someone who does know where to start and soak as much information from them as possible.
Phase 2Maintenance doesn't stop when the bug is fixed
When you're fixing something, ask yourself; how did this happen? Individuals make mistakes, but for a bug to make it to production means something in our process failed. Was there a QA involved in the development? How's the test coverage? Is there something in the codebase that is inherently confusing and often gets misused by devs?
Record the answers to this down somewhere, at the end of a maintenance stint you'll need to recall these details to share with the rest of the team.
Some of the problems you get will be really difficult. Getting a knowledgable teammate involved in debugging can often help you find the root cause for something quicker. I'm a serial rabbit hole explorer; pairing with someone stops me from wasting time on something unrelated.
Never forget that the bug you're fixing affects customers. Fixing their issue is a great start, but great communication with customers can really make a difference. Irate customers can be placated by a quick update on their issue; silence will only lead to more anger. The advocates are more than happy to help you with this.
In some cases fixing the bug isn't enough; be conscious of the pain the customer has felt. Often something small like a free month of OnDemand can help them forget about that time we almost deactivated their account.
Many of us are on teams dedicated to certain parts of our system landscape. Maintenance is your chance to branch out, learn things, and become a better developer.
Events Home
Events home
Pages
Blog
Questions
Calendar
?
SPACE SHORTCUTS
CHILD PAGES
Space Administration
Events Home
Events projects
AtlasCamp 2016
Summit 2016
Events decision log
Events
IntroductionThe goal of this marketing plan is to outline the strategies, tactics, and programs that will make the sales goals outlined in the fashion business plan a reality in the year 2015.
Maintenance is not about banging out as many fixes as you can in 2 weeks. There are several valid reasons for including someone who isn't on maintenance.
ObjectivesHave a plan and budget for FY2013 accounting for growth and marketing activites for the coming year.
Phase 1Warranty fix. If a team has pushed out their brand new feature and it's misbehaving then it's their responsibility to fix it. Don't just assign the ticket to them and call it a day. Contact the team (in person or via HipChat), explain what you're seeing, ensure that fixing the bug is the responsible team's highest priority.
The NFI condition. It's not uncommon to encounter an issue where you have no idea where to start. Again, don't give up and assign it to someone senior! This is your chance to learn! Pair with someone who does know where to start and soak as much information from them as possible.
Phase 2Maintenance doesn't stop when the bug is fixed
When you're fixing something, ask yourself; how did this happen? Individuals make mistakes, but for a bug to make it to production means something in our process failed. Was there a QA involved in the development? How's the test coverage? Is there something in the codebase that is inherently confusing and often gets misused by devs?
Record the answers to this down somewhere, at the end of a maintenance stint you'll need to recall these details to share with the rest of the team.
Some of the problems you get will be really difficult. Getting a knowledgable teammate involved in debugging can often help you find the root cause for something quicker. I'm a serial rabbit hole explorer; pairing with someone stops me from wasting time on something unrelated.
Never forget that the bug you're fixing affects customers. Fixing their issue is a great start, but great communication with customers can really make a difference. Irate customers can be placated by a quick update on their issue; silence will only lead to more anger. The advocates are more than happy to help you with this.
In some cases fixing the bug isn't enough; be conscious of the pain the customer has felt. Often something small like a free month of OnDemand can help them forget about that time we almost deactivated their account.
Many of us are on teams dedicated to certain parts of our system landscape. Maintenance is your chance to branch out, learn things, and become a better developer.
Finance Home
Finance home
Pages
Blog
Questions
Calendar
?
SPACE SHORTCUTS
CHILD PAGES
Space Administration
Finance Home
Finance projects
Q2FY17 Budget
Finance team goals
Finance decision log
Finance
IntroductionThe goal of this marketing plan is to outline the strategies, tactics, and programs that will make the sales goals outlined in the fashion business plan a reality in the year 2015.
Maintenance is not about banging out as many fixes as you can in 2 weeks. There are several valid reasons for including someone who isn't on maintenance.
ObjectivesHave a plan and budget for FY2013 accounting for growth and marketing activites for the coming year.
Phase 1Warranty fix. If a team has pushed out their brand new feature and it's misbehaving then it's their responsibility to fix it. Don't just assign the ticket to them and call it a day. Contact the team (in person or via HipChat), explain what you're seeing, ensure that fixing the bug is the responsible team's highest priority.
The NFI condition. It's not uncommon to encounter an issue where you have no idea where to start. Again, don't give up and assign it to someone senior! This is your chance to learn! Pair with someone who does know where to start and soak as much information from them as possible.
Phase 2Maintenance doesn't stop when the bug is fixed
When you're fixing something, ask yourself; how did this happen? Individuals make mistakes, but for a bug to make it to production means something in our process failed. Was there a QA involved in the development? How's the test coverage? Is there something in the codebase that is inherently confusing and often gets misused by devs?
Record the answers to this down somewhere, at the end of a maintenance stint you'll need to recall these details to share with the rest of the team.
Some of the problems you get will be really difficult. Getting a knowledgable teammate involved in debugging can often help you find the root cause for something quicker. I'm a serial rabbit hole explorer; pairing with someone stops me from wasting time on something unrelated.
Never forget that the bug you're fixing affects customers. Fixing their issue is a great start, but great communication with customers can really make a difference. Irate customers can be placated by a quick update on their issue; silence will only lead to more anger. The advocates are more than happy to help you with this.
In some cases fixing the bug isn't enough; be conscious of the pain the customer has felt. Often something small like a free month of OnDemand can help them forget about that time we almost deactivated their account.
Many of us are on teams dedicated to certain parts of our system landscape. Maintenance is your chance to branch out, learn things, and become a better developer.
Engineering Home
Engineering home
Pages
Blog
Questions
Calendar
?
SPACE SHORTCUTS
CHILD PAGES
Space Administration
Engineering Home
Engineering project plan
Engineering Teams
New starter guide
Decision log
Engineering
IntroductionThe goal of this marketing plan is to outline the strategies, tactics, and programs that will make the sales goals outlined in the fashion business plan a reality in the year 2015.
Maintenance is not about banging out as many fixes as you can in 2 weeks. There are several valid reasons for including someone who isn't on maintenance.
ObjectivesHave a plan and budget for FY2013 accounting for growth and marketing activites for the coming year.
Phase 1Warranty fix. If a team has pushed out their brand new feature and it's misbehaving then it's their responsibility to fix it. Don't just assign the ticket to them and call it a day. Contact the team (in person or via HipChat), explain what you're seeing, ensure that fixing the bug is the responsible team's highest priority.
The NFI condition. It's not uncommon to encounter an issue where you have no idea where to start. Again, don't give up and assign it to someone senior! This is your chance to learn! Pair with someone who does know where to start and soak as much information from them as possible.
Phase 2Maintenance doesn't stop when the bug is fixed
When you're fixing something, ask yourself; how did this happen? Individuals make mistakes, but for a bug to make it to production means something in our process failed. Was there a QA involved in the development? How's the test coverage? Is there something in the codebase that is inherently confusing and often gets misused by devs?
Record the answers to this down somewhere, at the end of a maintenance stint you'll need to recall these details to share with the rest of the team.
Some of the problems you get will be really difficult. Getting a knowledgable teammate involved in debugging can often help you find the root cause for something quicker. I'm a serial rabbit hole explorer; pairing with someone stops me from wasting time on something unrelated.
Never forget that the bug you're fixing affects customers. Fixing their issue is a great start, but great communication with customers can really make a difference. Irate customers can be placated by a quick update on their issue; silence will only lead to more anger. The advocates are more than happy to help you with this.
In some cases fixing the bug isn't enough; be conscious of the pain the customer has felt. Often something small like a free month of OnDemand can help them forget about that time we almost deactivated their account.
Many of us are on teams dedicated to certain parts of our system landscape. Maintenance is your chance to branch out, learn things, and become a better developer.
Marketing Home
Marketing home
Pages
Blog
Questions
Calendar
?
SPACE SHORTCUTS
CHILD PAGES
Space Administration
Marketing
Marketing Strategy CY…
Weekly Reports
Campaigns
Marketing Home
Campaign planning Fy16
IntroductionThe goal of this marketing plan is to outline the strategies, tactics, and programs that will make the sales goals outlined in the fashion business plan a reality in the year 2015.
Maintenance is not about banging out as many fixes as you can in 2 weeks. There are several valid reasons for including someone who isn't on maintenance.
ObjectivesHave a plan and budget for FY2013 accounting for growth and marketing activites for the coming year.
Phase 1Warranty fix. If a team has pushed out their brand new feature and it's misbehaving then it's their responsibility to fix it. Don't just assign the ticket to them and call it a day. Contact the team (in person or via HipChat), explain what you're seeing, ensure that fixing the bug is the responsible team's highest priority.
The NFI condition. It's not uncommon to encounter an issue where you have no idea where to start. Again, don't give up and assign it to someone senior! This is your chance to learn! Pair with someone who does know where to start and soak as much information from them as possible.
Phase 2Maintenance doesn't stop when the bug is fixed
When you're fixing something, ask yourself; how did this happen? Individuals make mistakes, but for a bug to make it to production means something in our process failed. Was there a QA involved in the development? How's the test coverage? Is there something in the codebase that is inherently confusing and often gets misused by devs?
Record the answers to this down somewhere, at the end of a maintenance stint you'll need to recall these details to share with the rest of the team.
Some of the problems you get will be really difficult. Getting a knowledgable teammate involved in debugging can often help you find the root cause for something quicker. I'm a serial rabbit hole explorer; pairing with someone stops me from wasting time on something unrelated.
Never forget that the bug you're fixing affects customers. Fixing their issue is a great start, but great communication with customers can really make a difference. Irate customers can be placated by a quick update on their issue; silence will only lead to more anger. The advocates are more than happy to help you with this.
In some cases fixing the bug isn't enough; be conscious of the pain the customer has felt. Often something small like a free month of OnDemand can help them forget about that time we almost deactivated their account.
Many of us are on teams dedicated to certain parts of our system landscape. Maintenance is your chance to branch out, learn things, and become a better developer.
Legal Home
Legal home
Pages
Blog
Questions
Calendar
?
SPACE SHORTCUTS
CHILD PAGES
Space Administration
Engineering Home
Engineering project plan
Engineering Teams
New starter guide
Decision log
Legal
IntroductionThe goal of this marketing plan is to outline the strategies, tactics, and programs that will make the sales goals outlined in the fashion business plan a reality in the year 2015.
Maintenance is not about banging out as many fixes as you can in 2 weeks. There are several valid reasons for including someone who isn't on maintenance.
ObjectivesHave a plan and budget for FY2013 accounting for growth and marketing activites for the coming year.
Phase 1Warranty fix. If a team has pushed out their brand new feature and it's misbehaving then it's their responsibility to fix it. Don't just assign the ticket to them and call it a day. Contact the team (in person or via HipChat), explain what you're seeing, ensure that fixing the bug is the responsible team's highest priority.
The NFI condition. It's not uncommon to encounter an issue where you have no idea where to start. Again, don't give up and assign it to someone senior! This is your chance to learn! Pair with someone who does know where to start and soak as much information from them as possible.
Phase 2Maintenance doesn't stop when the bug is fixed
When you're fixing something, ask yourself; how did this happen? Individuals make mistakes, but for a bug to make it to production means something in our process failed. Was there a QA involved in the development? How's the test coverage? Is there something in the codebase that is inherently confusing and often gets misused by devs?
Record the answers to this down somewhere, at the end of a maintenance stint you'll need to recall these details to share with the rest of the team.
Some of the problems you get will be really difficult. Getting a knowledgable teammate involved in debugging can often help you find the root cause for something quicker. I'm a serial rabbit hole explorer; pairing with someone stops me from wasting time on something unrelated.
Never forget that the bug you're fixing affects customers. Fixing their issue is a great start, but great communication with customers can really make a difference. Irate customers can be placated by a quick update on their issue; silence will only lead to more anger. The advocates are more than happy to help you with this.
In some cases fixing the bug isn't enough; be conscious of the pain the customer has felt. Often something small like a free month of OnDemand can help them forget about that time we almost deactivated their account.
Many of us are on teams dedicated to certain parts of our system landscape. Maintenance is your chance to branch out, learn things, and become a better developer.
Events Home
Events home
Pages
Blog
Questions
Calendar
?
SPACE SHORTCUTS
CHILD PAGES
Space Administration
Events Home
Events projects
AtlasCamp 2016
Summit 2016
Events decision log
Events
IntroductionThe goal of this marketing plan is to outline the strategies, tactics, and programs that will make the sales goals outlined in the fashion business plan a reality in the year 2015.
Maintenance is not about banging out as many fixes as you can in 2 weeks. There are several valid reasons for including someone who isn't on maintenance.
ObjectivesHave a plan and budget for FY2013 accounting for growth and marketing activites for the coming year.
Phase 1Warranty fix. If a team has pushed out their brand new feature and it's misbehaving then it's their responsibility to fix it. Don't just assign the ticket to them and call it a day. Contact the team (in person or via HipChat), explain what you're seeing, ensure that fixing the bug is the responsible team's highest priority.
The NFI condition. It's not uncommon to encounter an issue where you have no idea where to start. Again, don't give up and assign it to someone senior! This is your chance to learn! Pair with someone who does know where to start and soak as much information from them as possible.
Phase 2Maintenance doesn't stop when the bug is fixed
When you're fixing something, ask yourself; how did this happen? Individuals make mistakes, but for a bug to make it to production means something in our process failed. Was there a QA involved in the development? How's the test coverage? Is there something in the codebase that is inherently confusing and often gets misused by devs?
Record the answers to this down somewhere, at the end of a maintenance stint you'll need to recall these details to share with the rest of the team.
Some of the problems you get will be really difficult. Getting a knowledgable teammate involved in debugging can often help you find the root cause for something quicker. I'm a serial rabbit hole explorer; pairing with someone stops me from wasting time on something unrelated.
Never forget that the bug you're fixing affects customers. Fixing their issue is a great start, but great communication with customers can really make a difference. Irate customers can be placated by a quick update on their issue; silence will only lead to more anger. The advocates are more than happy to help you with this.
In some cases fixing the bug isn't enough; be conscious of the pain the customer has felt. Often something small like a free month of OnDemand can help them forget about that time we almost deactivated their account.
Many of us are on teams dedicated to certain parts of our system landscape. Maintenance is your chance to branch out, learn things, and become a better developer.
Finance Home
Finance home
Pages
Blog
Questions
Calendar
?
SPACE SHORTCUTS
CHILD PAGES
Space Administration
Finance Home
Finance projects
Q2FY17 Budget
Finance team goals
Finance decision log
Finance
ı
IntroductionThe goal of this marketing plan is to outline the strategies, tactics, and programs that will make the sales goals outlined in the fashion business plan a reality in the year 2015.
Maintenance is not about banging out as many fixes as you can in 2 weeks. There are several valid reasons for including someone who isn't on maintenance.
ObjectivesHave a plan and budget for FY2013 accounting for growth and marketing activites for the coming year.
Phase 1Warranty fix. If a team has pushed out their brand new feature and it's misbehaving then it's their responsibility to fix it. Don't just assign the ticket to them and call it a day. Contact the team (in person or via HipChat), explain what you're seeing, ensure that fixing the bug is the responsible team's highest priority.
The NFI condition. It's not uncommon to encounter an issue where you have no idea where to start. Again, don't give up and assign it to someone senior! This is your chance to learn! Pair with someone who does know where to start and soak as much information from them as possible.
Phase 2Maintenance doesn't stop when the bug is fixed
When you're fixing something, ask yourself; how did this happen? Individuals make mistakes, but for a bug to make it to production means something in our process failed. Was there a QA involved in the development? How's the test coverage? Is there something in the codebase that is inherently confusing and often gets misused by devs?
Record the answers to this down somewhere, at the end of a maintenance stint you'll need to recall these details to share with the rest of the team.
Some of the problems you get will be really difficult. Getting a knowledgable teammate involved in debugging can often help you find the root cause for something quicker. I'm a serial rabbit hole explorer; pairing with someone stops me from wasting time on something unrelated.
Never forget that the bug you're fixing affects customers. Fixing their issue is a great start, but great communication with customers can really make a difference. Irate customers can be placated by a quick update on their issue; silence will only lead to more anger. The advocates are more than happy to help you with this.
In some cases fixing the bug isn't enough; be conscious of the pain the customer has felt. Often something small like a free month of OnDemand can help them forget about that time we almost deactivated their account.
Many of us are on teams dedicated to certain parts of our system landscape. Maintenance is your chance to branch out, learn things, and become a better developer.
Engineering Home
Engineering home
Pages
Blog
Questions
Calendar
?
SPACE SHORTCUTS
CHILD PAGES
Space Administration
Engineering Home
Engineering project plan
Engineering Teams
New starter guide
Decision log
Engineering
API
Integrate
Create
Macros
Custom content
Page extensions Search extensions
Blueprints Theming
Patterns
Guiding principles for theming in the Cloud
Atlassian connection Maintain a connection
with users at a brand and support level in the Cloud
Sustainable API Enable flexibility but don’t
hinder Atlassian and vendors from moving fast
Consistent Core UX Provide consistency for
core experiences such as content collaboration
with or without themes
Flexible landing experience
Space landing experiences
Configurable content experience
Specialised space navigation
Theming Atlassian
JIRA Service DeskCustom portal experiences.
JIRALightweight branding where appropriate.
People DirectoryExperiences common to multiple products.
Cloud theming use cases
Reference Documentation References, guides, knowledge base, training etc.
Communities Intranets, extranets, micro-sites
Blog streams Reddit style blog streams
Project Collaboration Sharing progress with external stakeholders
Internal services HR, Legal, etc. for internal consumers
??? Your feedback!
Theming update Drew WalkerWed 3:10 PM
I N T E G R AT I O N PAT T E R N S
C O N F L U E N C E A P I
C R E AT I O N PAT T E R N S
D E V E X P E R I E N C E
Agenda
R O A D TO L A U N C H !
W O R K I N P R O G R E S S
Prime time!
Prime time!
Familiar add-ons migrating
Prime time!
Familiar add-ons migrating
New add-ons shipping fast
Prime time!
Familiar add-ons migrating
New add-ons shipping fast
Easy to get started
Prime time!
Familiar add-ons migrating
New add-ons shipping fast
Easy to get started
Rapidly growing marketplace
190% in 7 months
Prime time!
Familiar add-ons migrating
New add-ons shipping fast
Easy to get started
Rapidly growing marketplace
Significant user interest
Thank you to our beta partners!
Let’s do this!
Custom Content Steve Lancashire
Wed 3:35 PM
Theming update Drew WalkerWed 3:10 PM
Getting started Matthew Jensen
Wed 2:45 PM
UX Guidelines Brian Swift
Tue 4:05 PM
We’d love to hear from you!
KATE WEST-WALKER • DEVELOPER • @KAPWWBEN MACKIE • PLATFORM GUY • @BDMACKIE
http://bit.ly/confluence-connect-eoi
http://developer.atlassian.com
