AUG NYC May-24 event presentations
Download as PPTX, PDFâ˘1 likeâ˘290 views
The document discusses the importance of a standard methodology for managing configuration changes in Jira, emphasizing governance, change management, and adopting automation practices. It outlines best practices for controlling and documenting changes, promotes using tools like Jira Service Desk and ScriptRunner for efficient change requests and approvals, and highlights the need for well-planned configurations to reduce deployment issues. The overarching message is that automation and clear governance are vital for successful change management in Jira environments.
AUG NYC May-24 event presentations
- 1. BROUGHT TO YOU BY THE ADAPTAVIST TEAM Responsible Change Management on your Jira Instance As discussed in âThe Future of Atlassian Automationâ
- 3. Objective Introduce a standard methodology, process, and controls for managing configuration changes in Jira.
- 4. Business Problem How do you successfully control, document, and replicate changes into a production Jira environment.
- 5. Agenda ⢠Principles and Practices ⢠Solution Components ⢠Presentation Demo
- 6. Principle and Practices ⢠Institute Governance ⢠Change Management ⢠Configuration as Code ⢠Promotion Controls
- 7. Institute Governance ⢠Define common scheme sets ⢠Define standard nomenclature ⢠Configure project template to each scheme set ⢠Standardize/streamline project creation ⢠Maintain common configurations
- 9. Configuration as Code ⢠Standardize your environment ⢠Environment configuration should be automated ⢠Changes need to be version controlled ⢠Keep changes small and simple (KISS) ⢠Test your changes (CI/CD) throughout the process ⢠Changes need to be auditable
- 11. Solution Components Submit a request for Change Stage your Jira config changes Obtain Approval Push to Production
- 12. Submit a request for Change Stage your Jira config changes Obtain Approval Push to Production Solution Components
- 13. Configuration Change Request type(s)
- 15. Submit a request for Change Stage your Jira config changes Obtain Approval Push to Production Solution Components
- 16. Stage your Configuration Changes Track Changes Version control on configuration updates. Track configuration history Real Simulation Changes may require simulation with real world (production data) Well Formed Determine and document well designed and planned changes Impact & Risk Assess full impact on target instance. Beware of shared schemes and elements Validate Changes Test your changes
- 18. Service Desk Items Included and Queues
- 19. Submit a request for Change Stage your Jira config changes Obtain Approval Push to Production Solution Components
- 20. Use Jira to Approve your own Config Changes
- 22. Submit a request for Change Stage your Jira config changes Obtain Approval Push to Production Solution Components
- 23. But it worked in dev ⌠Itâs just a simple change ⌠Thatâs not what I asked for Who changed it? ⌠Can you change it back? Why are we still having so many issues deploying Jira changes?
- 24. What am I missing? Automation
- 25. Not Consistent Labor Intensive Risky Not Auditable Costly Manual Change Management Model
- 26. Agenda ⢠Principles and Practices ⢠Solution Components ⢠Demo
- 27. Get Approval Use JSD to request and obtain approval for your proposed configuration change Stage your Jira config changes Impact and Risk Analysis, Modify, Versioning and Validation Push to Production Use ScriptRunner & Project Configurator together to push the changes automatically to Production Submit request for change Define structured change requests for what types of changes are supported Demo Solution Component Leveraging JSD, Project Configurator, and ScriptRunner
- 28. PROJECT CONFIGURATOR 28 Add-on for moving projects and their configurations between Jira instances Change Management for Jira administration Launched to Marketplace in 2013 Joined Adaptavist suite of products in Summer of 2017 Over 2300 installations Supports
- 29. ScriptRunner for Jira 29 Add-on for extending and automating Atlassian Jira Launched to Marketplace in 2010 Joined Adaptavist suite of products in Summer of 2014 Almost 19,000 installations Supports Server and Cloud offerings. This solution is based on Server offering
- 31. Create new Request type
- 32. Extend SLA
- 33. Add Queue for new requests
- 42. After promoting
- 43. After promoting
- 44. After promoting
- 45. Summary â Configuration Change Management in Jira requires multiple best practices be adopted â Governance â Change control â Configuration as Code â Promotion control â Evolve standards in controlled manner â Automation is the key to eliminating the configuration change woes â Assign ownership of the shared configuration
- 46. References Automation for jira https://scriptrunner.adaptavist.com/latest/jira/plugins/automa tion-for-jira.html How to Automate export and load of project configurations: https://www.adaptavist.com/doco/display/PCP/How+to+auto mate+export+and+load+of+project+configurations
- 47. BROUGHT TO YOU BY THE ADAPTAVIST TEAM
- 48. Thank You and Questions? BROUGHT TO YOU BY THE ADAPTAVIST TEAM
- 49. First Time Jira Admin Tips Boris Berenberg @imatincr Atlasauthority.com
- 50. Why should I listen to him?
- 51. In the coal mines (of Atlassian support)
- 56. Agenda
- 57. 10,000 ft 1,000 ft 100 ft Infrastructure Misc Resources
- 58. 10,000 foot view
- 59. Limit number of admins
- 60. Jira follows business process Not the other way around
- 61. Draw Flowcharts
- 62. 1000 foot view
- 64. Standardized configuration objects: â Schemes â Fields â Workflows
- 65. Use a naming convention that includes object type
- 66. Use * OR + to show whatâs preferred
- 68. Use the Shared Configuration link when creating projects
- 70. Configuration Management tools are your friends
- 71. 00 foot view
- 72. Role based: Permission Schemes Notification Schemes Issue Security Schemes Workflows
- 74. Never have duplicate field names
- 75. Donât have fields that copy reserved JQL keywords type, project, and, or, is, empty, in, not, was, changed, null, order, by, request, savedFilter, searchRequest, id, issue, key, createdDate, dueDate, timeOriginalEstimate, timeEstimate, resolutionDate, updatedDate
- 77. Statuses != Resolutions Don't make Status fields
- 78. Make sure to auto set and clear resolutions in workflows
- 79. Don't fear simplified workflows
- 80. Infrastructure
- 81. SSL Termination should happen in a proxy
- 82. Utilize a configuration management tool like we use Puppet in our managed hosting
- 83. Have a* test environment
- 84. Misc
- 85. Be judicious with plugins Also, budget for them
- 90. Dog Food - Youâre available via the same tools others use
- 91. Read release notes even if you donât plan to upgrade
- 92. Subscription to JAC for critical issues
- 93. Resources
- 94. Community AUGs Team Tour / Summit Youtube CAC
- 95. Partners (like us *wink wink*)
- 96. Excellent books
- 97. Limit number of admins Jira follows business process Not the other way around Draw Flowcharts Understand object relationships Standardized configuration objects Use a naming convention that includes object type Use * OR + to show whatâs preferred Document Your System Publicly Use the Shared Configuration link when creating projects Configuration Management tools are your friends Role based: Permission Schemes, Notification Schemes, Issue Security Schemes, Workflows Never have duplicate field names Donât have fields that copy reserved JQL keywords type, project, and, or, is, empty, in, not, was, changed, null, order, by, request, savedFilter, searchRequest, id, issue, key, createdDate, dueDate, timeOriginalEstimate, timeEstimate, resolutionDate, updatedDate Use field contexts Statuses != Resolutions Don't make Status fields Make sure to auto set and clear resolutions in workflows Don't fear simplified workflows SSL Termination should happen in a proxy Utilize a configuration management tool like we use Puppet in our managed hosting Have a* test environment Be judicious with plugins Also, budget for them Brand the Instance Dog Food - Youâre available via the same tools others use Read release notes even if you donât plan to upgrade Subscription to JAC for critical issues Community, AUGs, Team Tour / Summit, Youtube, CAC Partners Excellent books Summary
- 98. Summary (28 tips) Limit number of adminsJira follows business process Not the other way around Draw Flowcharts Understand object relationshipsStandardized configuration objects Use a naming convention that includes object type Use * OR + to show whatâs preferred Document Your System PubliclyUse the Shared Configuration link when creating projects Configuration Management tools are your friends Role based: Permission Schemes, Notification Schemes, Issue Security Schemes, Workflows Never have duplicate field names Donât have fields that copy reserved JQL keywords type, project, and, or, is, empty, in, not, was, changed, null, order, by, request, savedFilter, searchRequest, id, issue, key, createdDate, dueDate, timeOriginalEstimate, timeEstimate, resolutionDate, updatedDate Use field contexts Statuses != Resolutions Don't make Status fields Make sure to auto set and clear resolutions in workflows Don't fear simplified workflows SSL Termination should happen in a proxy Utilize a configuration management tool like we use Puppet in our managed hosting Have a* test environmentBe judicious with plugins Also, budget for them Brand the Instance Dog Food - Youâre available via the same tools others use Read release notes even if you donât plan to upgrade Subscription to JAC for critical issues Community, AUGs, Team Tour / Summit, Youtube, CAC Partners Excellent books
- 99. "Stay calm and do not despair!" - Sebastian Kleinholz
- 100. How did I do? Would you recommend this talk? I love feedback. [email protected] @imatincr
Editor's Notes
- #2: First off, I want to welcome all of you and thank you for attending this workshop today. Weâre very excited to spend time with you all and discuss how youâre utilising the concept of automation today and what the future holds for the industry and development teams across boarders. A bit of housekeeping â WIFI: Agenda: ââ TELL EVERYONE WHAT THE AGENDA IS FOR THE DAY ââ With that said, letâs introduce ourselves properly
- #6: Principle and practices of Change management Soluton component that will make up a change management configuration for your jira changes And we will wrap it up with a presentation demo
- #7: First off, I want to welcome all of you and thank you for attending this workshop today. Weâre very excited to spend time with you all and discuss how youâre utilising the concept of automation today and what the future holds for the industry and development teams across boarders. A bit of housekeeping â WIFI: Agenda: ââ TELL EVERYONE WHAT THE AGENDA IS FOR THE DAY ââ With that said, letâs introduce ourselves properly A peek preview of the automation that adaptavist if creating for the atlassian tools
- #8: Institute Governance Define common scheme sets - shared schemes for workflows, issue types, screens, permissions, notifications, etc. Define standard nomenclature â adopt naming conventions for field, issues, projects, schemes, etc. Configure project template to each scheme set - templates for development (scrum, kanban, hybrid) task management, service, non-IT/dev projects Standardize/streamline project creation - Create new projects from template Maintain common configurations - All changes applied against a shared configuration. Avoid bespoke configurationsÂ
- #9: Standards Well documented Controlled Changes Single source of record (everything comes through one stop) Board of review to accept changes Changes based against a set of standards
- #10: Configuration as code: Allows the entire configuration of Jira to be treated and stored as source code Automation and Standardization Versioning of Changes Traceability of Changes Smooth promotion of changes from Development to Production environments Provides team the ability to keep environments in synch Environment configuration should be automated Changes need to be version controlled Keep changes small and simple (KISS) Test your changes (CI/CD) throughout the process
- #11: Make life easier for Jira and Project Admins Follow Change Management Best Practices for your Jira Project Configs Automate the push of changes from development to staging to Production These are the principle and now how do we build a solution using these principles
- #12: Here are different components to the solutions - Submit a form change request
- #13: First off, I want to welcome all of you and thank you for attending this workshop today. Weâre very excited to spend time with you all and discuss how youâre utilising the concept of automation today and what the future holds for the industry and development teams across boarders. A bit of housekeeping â WIFI: Agenda: ââ TELL EVERYONE WHAT THE AGENDA IS FOR THE DAY ââ With that said, letâs introduce ourselves properly A peek preview of the automation that adaptavist if creating for the atlassian tools
- #14: Use Jira Service Desk to Request Approval of a Jira Config Change Implementation process
- #16: First off, I want to welcome all of you and thank you for attending this workshop today. Weâre very excited to spend time with you all and discuss how youâre utilising the concept of automation today and what the future holds for the industry and development teams across boarders. A bit of housekeeping â WIFI: Agenda: ââ TELL EVERYONE WHAT THE AGENDA IS FOR THE DAY ââ With that said, letâs introduce ourselves properly A peek preview of the automation that adaptavist if creating for the atlassian tools
- #17: Want to have : Well formed â Document what need to be done
- #18: Make configuration changes in your staging Jira instance. This could be any number of changes like: Add a new issue type to your project Tweak your workflow Update a screen or 2 Introduce new Versions or Components Almost any configuration change you can think of for a Jira Project Add a field
- #19: Make configuration changes in your staging Jira instance. This could be any number of changes like: Add a new issue type to your project Tweak your workflow Update a screen or 2 Introduce new Versions or Components Almost any configuration change you can think of for a Jira Project
- #20: First off, I want to welcome all of you and thank you for attending this workshop today. Weâre very excited to spend time with you all and discuss how youâre utilising the concept of automation today and what the future holds for the industry and development teams across boarders. A bit of housekeeping â WIFI: Agenda: ââ TELL EVERYONE WHAT THE AGENDA IS FOR THE DAY ââ With that said, letâs introduce ourselves properly A peek preview of the automation that adaptavist if creating for the atlassian tools
- #21: Use Jira Service Desk to Request Approval of a Jira Config Change Who get to approval Approval process
- #22: Use a Jira Workflow to get your change approved Then use a ScriptRunner Post-Function to check the approval was done and push your changes to production automatically Level of complexity, effort, and risk for the type of level of approval
- #23: First off, I want to welcome all of you and thank you for attending this workshop today. Weâre very excited to spend time with you all and discuss how youâre utilising the concept of automation today and what the future holds for the industry and development teams across boarders. A bit of housekeeping â WIFI: Agenda: ââ TELL EVERYONE WHAT THE AGENDA IS FOR THE DAY ââ With that said, letâs introduce ourselves properly A peek preview of the automation that adaptavist if creating for the atlassian tools
- #24: Are there any Admins in the audience. How many times have you had a jira change failed Who has experienced an unsuccessful Jira implementation What was some of the causes What was the outcome
- #25: This is how the the automobile factory floor looked 100 years ago. And this was considered a cornerstone of the industrial revolution. The same can be said with JIRA changes - No Controls Manually Labor Intensive No Audit No History Any color as long as it black Email request Sneaker net request
- #26: This is how the the automobile factory floor looked 100 years ago. And this was considered a cornerstone of the industrial revolution. The same can be said with JIRA changes - No Controls Manually Labor Intensive No Audit No History Any color as long as it black Email request Sneaker net request
- #27: First off, I want to welcome all of you and thank you for attending this workshop today. Weâre very excited to spend time with you all and discuss how youâre utilising the concept of automation today and what the future holds for the industry and development teams across boarders. A bit of housekeeping â WIFI: Agenda: ââ TELL EVERYONE WHAT THE AGENDA IS FOR THE DAY ââ With that said, letâs introduce ourselves properly A peek preview of the automation that adaptavist if creating for the atlassian tools
- #28: In this demo we are using a: Request Management tool â Jira Service Desk or JIRA Tool that manages your project configuration â tools like Project Configurator or Boltron Tool that enable you to automate the promotion of changes between jira instances â tools Script Runner or puppet/chef and Rest API ScriptRunner and Project Configurator can now help Jira and Project Admins manage Jira projects in a much more controlled way! Now you can follow Change Management Best Practices on your own Jira projects! ScriptRunner and Project Configurator ???? allows you to: Submit change request Make changes in dev and staging Get approval for those changes Push them to production
- #48: How to use ScriptRunner and Project Configurator to automate changes to your Project Configurations
- #49: How to use ScriptRunner and Project Configurator to automate changes to your Project Configurations
- #53: Uber, Zenefits, Priceline, Helped write tests, 13 years in IT
- #56: Uber, Zenefits, Priceline, Helped write tests, 13 years in IT
- #57: Uber, Zenefits, Helped write tests, 13 years in IT
- #61: Why: Too many cooks in the kitchen How: Cooperate and support the teams effectively
- #62: Why: Not doing this causes friction between tool and users How: Work with the stakeholders closely
- #63: Why: Gets everyone on the same page How: Tools / Whiteboard
- #65: Why: troubleshoot and engineer new solutions without resorting to antipatterns How: Practice this in staging
- #66: Why: Makes your job easier, keeps system performant How: Invest time up front in making good objects
- #67: Why: UI can get confusing How: See the slide1
- #68: Why: makes admin work faster How: See slide
- #69: Why: Allows users to work with you How: I use SQL and then just dump it into Conf, Screenshots are also an option
- #70: Why: Because it helps to keep total number of objects in check
- #71: How: Use the highlighted links
- #74: Why: Scales, allows projects to self govern
- #76: Why: Horrible UX for both yourself, and your end users How: Documentation, small admin team
- #78: Why: Supports scale How: Map fields only to projects where they are used
- #79: Why: Keeps things cleaner, especially reporting How: Just donât name them the same
- #80: Why: for jira to understand status How: Post functions
- #81: Why: easy to use for end users How: Make one
- #82: Explain that this is for server admins
- #83: Why: Easier long term maintenance How: Follow docs from CAC
- #84: Why: Consistency and ease of use
- #85: One is a must, more is better
- #87: Talk about new project requests and custom fields
- #92: Give Example usage
- #93: Why: Because you may find out youâre being impacted by a bug you didnât even know about
- #94: Explain what JAC stands for Explain how you built it
- #96: Community is like Stack Overflow for Atlassian Explain what CAC stands for
- #101: Not sure who he is, but I liked his comment on Community