OCA
[16.0][ADD] project_scrum
Hi, this addon allow you to manage your project with scrum methodology.
You can access the sprints and blacklog from the project options on kanban view or from the project settings form view.
On the backlog view you found the all task for this project, except the task with kanban state is done or task with a sprint assigned.
On the sprint view you see the all sprint for this project.
- The sprint's have a timeline view.
- You can see your task from sprint.
- When a task have a sprint assigned, only can assigned the members on task.
On Sprint Timeline view you can found the task group by sprint.
You can change the sprint state with buttons on sprint form view or using the cron.
Added a new filter on search task for filter using a sprint state.
This PR has the approved label and has been created more than 5 days ago. It should therefore be ready to merge by a maintainer (or a PSC member if the concerned addon has no declared maintainer). 🤖
Nice work, but it's worth considering that a sprint can sometimes span multiple projects, particularly in contexts where teams manage several projects concurrently or employ scaled agile practices like SAFe. In these cases, linking sprint backlog items to their respective projects can optimize organization and progress tracking across initiatives.
References:
https://scaledagileframework.com/#largesolution https://scaledagileframework.com/safe-scrum/ https://scaledagileframework.com/iteration-planning/
@mileo So I think what this technically entails is making project_id on project.sprint a many2many. What do you think @adasatorres? Would this be something you like?
Or we can use project_parent for this?
When the field is empty the sprint can be considered company-wide.
@adasatorres I made a PR to your branch can you please take a look :) https://github.com/BinhexTeam/project/pull/1
This PR has the approved label and has been created more than 5 days ago. It should therefore be ready to merge by a maintainer (or a PSC member if the concerned addon has no declared maintainer). 🤖
What a great day to merge this nice PR. Let's do it! Prepared branch 16.0-ocabot-merge-pr-1329-by-pedrobaeza-bump-nobump, awaiting test results.
Congratulations, your PR was merged at 6d8bb29f270698186275accddadadf68f3f0cbb2. Thanks a lot for contributing to OCA. ❤️
So is this https://github.com/OCA/project-agile/blob/14.0/project_scrum/ officially discontinued now? It's not a good idea to have two modules with the same name in different OCA repositories.
Oh, I wasn't aware of that one... Maybe we should move this one to there?
Well, if project-agile is not thought to be superfluous, it would rather belong there. But there is already a module with the same name and different code. So they should either be merged (and ideally a migration provided for existing installations) or one has to be renamed (which should be done anyway in order to avoid confusion and update problems with the older module). There is an open PR for the 16.0 port of the older module: https://github.com/OCA/project-agile/pull/39
Hello @pedrobaeza, we are using the https://github.com/OCA/project-agile/ also. We are also in the work of adding epics ( https://github.com/OCA/project-agile/issues/41 ) to that line of agile module. These already take care of sprints, user story ( and storypoints concept ) and now will also get epics (all in 14). Then we will migrate all of it in 16, but there is already some work going on for the migration: https://github.com/OCA/project-agile/pull/39 and https://github.com/OCA/project-agile/pull/38 . Have a look @adasatorres. Please keep us informed so we get a uniform agile line of module in 16 OCA. We would like to contribute to the version that will last throughout versions of odoo like https://github.com/OCA/project-agile/ did since 10.
I don't see the advantages of having the scrum modules in a different repository, IMO we should consolidate them and move functionality that is missing here
Good evening, first of all, I would like to apologize for the commotion caused by this incident. Secondly, the main idea behind this addon was to create a simpler version, as upon reviewing the project_scrum addon in the project_agile repository, I found elements that I don't believe are truly necessary or that, personally, don't make sense to me.
If it is necessary to include this addon in project-agile, is it possible to refactor the project_scrum from that repository?
The discussion here seems to have stalled. Sorry to bother everybody again, but can we somehow address the situation with the same module name? It is rather unfortunate and has caused some confusion and problems in our CI. Currently we must take care to prune the new module from the OCA repos, as some database instances use the old one and the data models are of course not compatible. It's one of a couple of differences we have to manage regarding OCA repositories, and I really would like to reduce these kind of differences. I'm also not sure if this is the right channel to discuss this; perhaps the discussion was continued at some other place?