Roles & Responsibilities

Action	Super User	Manager	Developer	Promoter
Add Server	✓
Create Project	✓	✓
Create Repository	✓	✓	✓
Clone Repository	✓	✓	✓
Commit Repository	✓	✓	✓
Switch Commit	✓	✓	✓
Create Merge Request	✓	✓	✓
Approve Merge Request	✓	✓
Create Jobs	✓	✓
Run Jobs	✓	✓		✓
Rollback Jobs	✓	✓		✓
Track & Compare Changes	✓	✓	✓

Developer's Journey

Before diving into the developer's journey, it's important to note that the manager sets the initial groundwork by creating projects, and assigning developers to specific projects within the Code Management platform. With this structure in place, the developer takes charge of their assigned project, beginning with the creation of a repository for their Qlik Sense application. This repository serves as the foundation for their development tasks, enabling them to efficiently collaborate and manage their work.

From there, the developer proceeds with the following responsibilities:

Cloning and Branching: They clone the application repository from the master branch and create dedicated branches (e.g., application_version1) to isolate changes and developments.
Development and Testing: Using Qlik Sense app editor or Qlik Sense Desktop, they implement necessary modifications to the application. Thorough testing ensues to ensure compliance with requirements, data accuracy, and functional integrity.
Version Control: Throughout the development process, the developer commits changes with clear and descriptive messages, documenting their progress. They leverage Code Management functionalities to track and compare changes between branches, ensuring transparency and accountability.
Merge Request Submission: When satisfied with their changes, the developer sends a merge request to the manager for integration into the main branch. This marks the culmination of their development efforts for a particular feature or iteration. However, if issues are identified, the manager may reject the request, providing detailed feedback. The developer addresses the manager's feedback, making necessary adjustments to their application. They then resubmit the merge request for further review. This iterative process continues until the manager approves the changes for integration into the main branch.

Developer's Capabilities

Create repositories for Qlik Sense applications within designated projects(streams).
Clone repositories to initiate development work.
Commit changes to repositories, with descriptive messages for documentation purposes.
Generate various versions of Qlik Sense applications to accomdate iterative development.
Track and compare changes between versions to ensure consistency and quality.
Create merge requests for integration into the main branch.

Manager's Journey

Project Creation and Team Management

The manager creates projects within the Code Management platform for different development teams or streams of work.
They assign roles and access levels to team members, ensuring appropriate permissions and responsibilities are established.

Merge Request Inspection and Resolution

As developers submit merge requests for review, the manager inspects merge conflicts and evaluates new changes within the platform.
They meticulously review code changes, ensuring they align with project goals, quality standards, and compliance requirements.
Based on their assessment, the manager resolves merge requests by either approving or rejecting them, providing detailed feedback when necessary.

Job Creation for Code Movement

To facilitate code movement between environments, the manager creates jobs within the Code Management platform.
These jobs define the process and parameters for transferring code from one environment to another, ensuring consistency and reliability in deployment.

Manager's Capabilities

Create projects(streams) to organize development efforts.
Assign roles and access to the project members.
Inspect merge conflicts and new changes.
Resolve merge requests from developers.
Create jobs to automate code movement between environments.
Also, they have comprehensive access to all developer funtionalities.