Jira Customization: Finding the Perfect Balance
2 likes7,569 views
The document outlines best practices for customizing Jira within teams at HP, emphasizing the importance of starting small, standardizing processes, and maintaining backward compatibility when implementing changes. It advises on team structure, including limiting the number of admins, and encourages engaging stakeholders in discussions regarding customization challenges. Additionally, it provides tips on reporting and the significance of documentation to facilitate future Jira administration.
Jira Customization: Finding the Perfect Balance
- 1. TANYA GORDON | ATLASSIAN TEAM TECH LEADER | HP Jira Customization Finding the Perfect Balance
- 5. Israeli âBeresheetâ first space craft lands on the moon (www.spacewatch.global)
- 6. Photo by Kari Shea on Unsplash
- 7. Photo by Daria Nepriakhina on Unsplash
- 8. Photo by Edwin Andrade on Unsplash
- 9. Customization Categories Out Of the Box Custom fields, workflows, issue types & more
- 10. Customization Categories Out Of the Box Custom fields, workflows, issue types & more Apps From the Atlassian Marketplace
- 11. Customization Categories Out Of the Box Custom fields, workflows, issue types & more Apps From the Atlassian Marketplace In-house Development Using scrips or a full app development
- 12. Jira Admin Team
- 13. Jira Admin Team Jira Admin Team Create a GREAT team and adjust team membersâ roles Invest in Atlassian certifications Atlassian Team
- 14. Number of Admins Number of Admins Keep it under 5 Atlassian Team
- 15. Delegate Delegate Use Project Administrators as your professional extension Atlassian Team
- 16. Look for the of the requirement
- 17. My group is broken ! RACHEL WRIGHT, JIRA STRATEGY ADMIN WORKBOOK
- 19. DETERMINE THE IMPACT NOW AND IN THE FUTURE
- 22. POOR PRACTICES Wrong Status Category for Similar Statuses
- 23. Standards at HP Sprint naming convention Sprint names include dates
- 24. Standards at HP Centralized versions list All teams use the same versions list, only specific stakeholders have update permissions
- 25. Standards at HP Jira forum Gather all relevant stakeholders to discuss Jira customization challenges and solutions
- 26. Don't start with a full blown customization at once Photo by Ryan McGuire on gratisography.com
- 28. CUSTOMIZATION PLANNING AND EXECUTION PROCESS
- 29. There are no limits, everything is possible, but not everything should be done... www. spacewatch.global
- 30. Clean up Photo by Oliver Hale on Unsplash
- 31. Clean-up Tips Apps and Tools Cleaner for Jira - Performance App Custom Fields Optimizer for Data Center
- 32. Clean-up Tips Custom field context No warning message is displayed on delete
- 33. Clean-up Tips Updated issues Might affect filters, views and integrations
- 38. Online Archiving Hide or mark as Read Only using permission scheme Offline Archiving Backup and Delete the project completely Project archiving work arounds For Jira Server, Cloud and older Data Center versions
- 39. Reporting
- 40. Filters and Dashboards JQL queries and a variety of dashboard gadgets
- 41. Filters and Dashboards JQL queries and a variety of dashboard gadgets Jira Board Reports Out-of-the-Box not customizable reports
- 42. Filters and Dashboards JQL queries and a variety of dashboard gadgets Jira Board Reports Out-of-the-Box not customizable reports External Apps or BI systems EazyBI, PowerBI, All-In-One Reports for Jira and moreâŠ
- 43. Reporting Customization Considerations Generic fields statuses and versions
- 44. Reporting Customization Considerations Generic fields statuses and versions Appropriate type
- 45. Reporting Customization Considerations Generic fields statuses and versions Appropriate type Master reports deck
- 47. Backward Compatibility Not only for upgradesâŠ
- 48. Backward Compatibility Check apps compatibility Make sure that new apps are compatible with existing solutions and reporting tools
- 49. Backward Compatibility Read ALL Release Notes The devil is in the details so read carefully and donât skip on versions
- 51. Backward Compatibility Testing Environment Three-tier strategy is best Dev -> Staging -> Production
- 52. www.devrant.com
- 53. You should always aim for simplicity to be able to scale SCALING CUSTOMIZATIONS
- 56. Adjust customizations to support Data Center SCALING CUSTOMIZATIONS
- 59. Do right by the next Jira admin
- 61. Service Desk Better support your users and keep all requests documented and managed.
- 62. THE CHECKLIST Standards Think Simple and Generic Start small and expand gradually Always look for the heart Test backward compatibility Document everything
- 64. TANYA GORDON | ATLASSIAN TEAM TECH LEADER | HP Thank you!