More or less suitable GitLab CE.
- Open and free
GitLab CE (Community Edition) is open and free. (There is also GitLab EE: open, but paid.)
- Ability to deploy on your hosting
Yes, but you can use the cloud.
- Uses scrum methodology
<режим-зануды>
People still use Scrum, and software can support it or at least not interfere. </режим-зануды>
Bore </режим-зануды>
Let's go over the practices of Scram and see which ones are supported.
Tasks
- There is an opportunity to start tasks in the tracker. The tracker is tied to the repository with the project. If you need a tracker by itself, you can create an empty project.
- The task has a unique number, title, description, comments, links to other tasks and Merge-Requests, author and performer.
- The tasks themselves can be described as user stories (user stories) , you can add DoD (Definition of Done, readiness criterion) to them and anything else, but all this will be in the same text field (i.e. you cannot have custom fields in the task, as in JIRA).
- The importance and category of the task can be identified using tags.
- So far, tasks have no hierarchy, it is possible that it will appear .
- You can use templates for tasks and Merge-Requests. This helps to standardize their appearance and content.
- Tasks do not have a date binding, so the calendar cannot be replaced.
In one of the latest releases, it became possible to organize tasks into so-called “problem boards” (issue boards). They are similar to kanban, but more flexible. There may be several boards, for example, on one you divide tasks between backlog and sprints, and on the other you track the execution inside the sprint.
Planning and Feedback
If you want to separate tasks by sprints, you can use Milestone for this. In GitLab itself, they are used to delimit releases - an example .
Evaluation of tasks in time seems to be missing. There is a feature to track time spent - Time tracking - but it comes as a separate product.
allows you to follow the general course of the project (and not everything is hidden in the rollers like in Trello), the status of the tasks, the efficiency of time use (graphs, charts - that's all)
There is Cycle Analytics - analytics of software production cycles. Shows data about the speed with which tasks are performed and at what stages it takes how much time. Read more in the documentation .
Roles
In GitLab there are users, there are levels of rights in the project. I don’t quite imagine what software support is needed to fulfill these roles. Is it possible to limit the rights to create tasks, labels milestone'ov.
Meetings
Again, I can not imagine how you can support this practice. The exception is the planning process, but it has already been mentioned above.
- It looks like a Trello, but more flexible in its settings and intuitive.
Did not work with Trello, I can not compare.