JIRA Development
0 likes777 views
JIRA is a bug tracking and issue tracking tool that allows users to manage issues, workflows, users and security. It also has a powerful plugin system that allows for customization. The document discusses building custom plugins and modules for JIRA, including different plugin module types. It also covers challenges like migrating configurations between environments and building custom data models and fields in JIRA.
JIRA Development
- 1. JIRA Development What is JIRA? What can we do with it? #Sperasoft_Talks:
- 2. Intro: what is JIRA? Custom system over JIRA in comparison JIRA plugin development Plugin module types Plugin module description Interesting problems: Configuration migration Building data model scheme in JIRA Agenda
- 3. What is JIRA? bugtracker What does JIRA have? issues workflows user management security great configuration & customization ability Intro
- 4. What does custom System have? entities workflows user management security reports other systems integration Intro (cont’d)
- 5. Habitual interface Simple Atlassian products integration other JIRA Confluence Flexible configuration (issue types, custom fields, workflows, events & mail) Powerful plugin system Community with developers (sometimes) Custom system over JIRA
- 6. Proprietary source code Issues linking scheme No consistency (custom fields implementation) Velocity templates hell Custom system over JIRA (cont’d)
- 7. Atlassian Plugin SDK (with Maven2 & Tomcat7) Plugin - *.JAR, contains of modules FastDev saves your time atlassian-plugin.xml – core plugin configuration file Lots of plugin module types Plugin Development
- 8. Web item, Web section Web panel REST Servlet Workflow customization (post functions, conditions, validators) Custom field type Component Many others… Plugin Module Types
- 9. Unique key Name, description Implementation class name Template files Parameters Plugin Module Description
- 11. Follow us on Twitter @Sperasoft Visit our site: sperasoft.com
- 12. Configuration migration Data Model. One-to-many, many-to- many schemes for issues Interesting Problems
- 13. Projects Issue types & schemes Statuses Resolutions Workflows & schemes Screens Screen configurations & schemes Custom fields Custom field configurations & schemes Project roles Security schemes Events Configuraion Migration
- 14. Goals: migrate configuration Dev -> Test -> Sandbox -> Production apply configuration to a clean JIRA instance Complexities: replace all IDs with names JIRA configuration API hell Configuraion Migration
- 15. Schema: configuration model with JAXB annotations to produce XML converters for configuration entities replacers for IDs and names reader and Writer that iterate configuration entities and read or write them Result: 1 MB xml file Configuration Migration (cont’d)
- 16. Database tables: customfield customfieldoption customfieldvalue Value types storage: Limited text Unlimited text (clob) Numeric Date Data Model
- 18. Solution: Field: using AbstractSingleFieldType class with SortableCustomField interface store issue’s ID many-to-one – custom field with one value many-to-many – custom field with multiple values Searcher: using AbstractInitializationCustomFieldSearcher class and lots of utility classes providing search info. Data Model (cont’d)
- 19. https://developer.atlassian.com https://answers.atlassian.com http://j-tricks.com JIRA Development Cookbook Docs
- 20. Have a question? Like this deck? Just follow us on twitter @Sperasoft Thanks!