Hauke Wollentin

Client's Goals:After a merger of four companies, various smaller Atlassian Data Center and Cloud instances were to be consolidated into one large instance per tool.

Project Impact:Reduction of license costs by ~50% and unified, collaborative work for all employees in a single toolstack.

An initial inventory was carried out for each smaller Jira and Confluence instance. Project and space managers were appointed, and a preliminary selection was made on paper regarding which content needed to be migrated and which archived.

In addition to the actual content, an analysis was performed on which workflows, screens, issue types, etc., could be consolidated during the migration. This was to avoid "duplicate code."

Scripts were created in ScriptRunner to, among other things, repair broken hard links or user references caused by the migration.

The migrations were primarily Data Center to Data Center; for each tool, a migration from Cloud to Data Center was performed.

To minimize the impact on employees, most content was migrated in small chunks (at the project or space level) in close coordination with stakeholders.

Client's Goals:As part of a pilot project for agile working methods, two teams were to be guided from scratch to a Scrum process using Jira Cloud. Furthermore, during the transformation, an Excel-based "ticket list" with several tens of thousands of lines was to be transferred into a Jira project to serve as a showcase for Jira within the company.

Project Impact:Awareness for agile working methods was created, leading to more transparency within the teams and also in upper management, thereby minimizing error vectors in project planning and increasing overall planning efficiency.

After two teams from product development were nominated for the pilot project "Introduce Scrum," a requirements list for Jira was created based on key user discussions, and potential plugins to be used were identified.

Jira Cloud was planned and set up for the majority of the company.

A group and permission concept was developed and implemented directly.

Parallel to the Scrum enablement, the project teams and other stakeholders were individually trained in Jira.

Screens, workflows, issue types, etc., were adapted or created according to the respective team requirements. Simple rules were created using Jira Automation to assist the teams in their daily work.

As a side quest, a PoC was created to map a historically grown Excel list into Jira, allowing employees to work on it collaboratively and each list item to become an independent object (instead of using the entire Excel list as one entity, thus "blocking" colleagues).

Client's Goals:The service catalog, previously maintained in Confluence, was to be implemented in Jira using Assets as the data basis.

Project Impact:Data integrity and quality were increased. Service data could be read programmatically, which benefited other projects and especially technical deployments. Lifecycle management and an approval process adapted to the company could be cleanly mapped in the UI.

Initially, all services and their components for delivery were transferred into a new data structure within Jira Assets.

A dedicated Jira project was then created for the "UI" for managing the services. Services were to be managed in a ticket rather than in the less intuitive Assets backend.

ScriptRunner Behaviors were developed that could load data directly from Assets into screens and save it back.

A custom-adapted approval process was developed and implemented. This allowed for the selection of individual persons as well as entire teams (with the option for any number of team members to approve) to approve or reject a service, for example, in the lifecycle process.

To make approvals graphically visible, a Custom Panel was built into the ticket view using ScriptRunner, showing who had already approved, how many approvals were still missing, and which ones (in the appearance of a traffic light system).

A REST endpoint was created to make services programmatically available. This was used, among other things, in Terraform's HTTP Provider to tag deployments for monitoring and billing.