Efficiently organizing thousands of users can be a real challenge for IT administrators. Keeping track of them across multiple Atlassian products...
The beginning of LeasePlan's Atlassian journey
In the previous project update, our certified consultants from venITure have already implemented proprietary solutions within a proof of concept. With the help of a detailed presentation, we were able to show and explain the current status and the implemented functionality to the team from LeasePlan Germany.
Of course, the requirements of the LeasePlan team were always decisive for the use of Jira and Confluence as project management tools, because only the user knows which tasks he wants to have fulfilled within the tool. A detailed exchange took place, in which the exact use of the tools and the resulting possibilities were discussed. Especially with regard to the various reporting functions of both Jira and Confluence, the LeasePlan team was enthusiastic about the functionality offered by Advanced Roadmaps for Jira. The ability to display tickets directly from Jira in a Gantt chart that can be worked with interactively was particularly well received. In addition, the seamless integration of Advanced Roadmaps in Jira makes it easy to directly adjust ticket data and make corresponding planning changes.
Preparation for the migration in Jira & Confluence
Introduction to Jira
During the training of the LeasePlan team, the focus was initially on project documentation in Confluence and the corresponding connection to Jira. The Atlassian tool ecosystem offers a seamless interface for this. This ensures that one of LeasePlan's most important requirements, namely clear and above all comprehensible documentation of the project, is implemented.
Introduction to Confluence
In the further course of the training, the focus shifted to the topic of "Confluence as the main storage location for project-related documentation". In this area, Confluence not only offers the possibility to store content on pages, but also to store files and even to reference ticket information from Jira. This means that the project documentation is not only static, but also interactive and always up-to-date. Confluence macros as tools offer a number of functions that can be installed as plug-ins for the implementation of a Confluence page. Above all, the LeasePlan team was delighted by macros such as "Attachments" or "Jira". With the use of "Attachments" you can get an overview of the attachments that are stored on the current page.
Migration of the existing projects
The project "NM"could be integrated directly into the Jira instance. To make this process compatible with venITure's own solution, a project ticket first had to be created.
From the ticket, an automation could be executed that converts the ticket itself into an independent project. The background to this procedure is that it gives the user of the project a contact point where the progress of the project is recorded centrally and comprehensibly in the form of a ticket.
After this was done, the individual requirements that were placed on the project had to be created as tickets. One of the requirements was to create a task type called "work package". This work package should function as a superordinate task in a project and be assignable. The graphic shows a possible task hierarchy.
With the help of the function "Parent Link" in Jira, tickets can be assigned to "children" or "parents", i.e. superordinate or subordinate to other tickets.
The migration of further projects proceeded similarly to the "NM" project already mentioned.
Confluence is one of the most important team workspaces your organization will ever use. Your team can share work, organize vital information and...