If I am correct the stage_id is in 'maintenance.request' and 'maintenance.request' is in 'maintenance.team'
If that the case, I think the problem is about how are you grouping your data
That is when you try to group the teams by stages you will end up with same team appear in many stages, because it has different requests in these stages.
but if you still want to group your team by this way, you need to have a stages field in the team model so that you used it for grouping
stages = fields.Many2many('practice.maintenance.stage', compute='_compute_team_stages', store=True)
@api.depends('request_ids.stage_id')
def _compute_team_stages(self):
for team in self:
team.stages = team.request_ids.stage_id
With regard to the kanban view you can use the above defined field(stages) as a value for default_group_by so that kanban will use it for grouping by default. or you can put it in the search view as a filter in the group tag.
kanban will display whatever grouping you provide, so if you have multiple groups you can define all of them in the search view
@m-azzain
i just found solution. In app maintance in field 'stage_id' there was a parameter:
group_expand='_read_group_stage_ids'
and in this function programm chooses all stages.
At start i think, that it is default and try to fix this and do it like in project app. I feel so dumb now)
Now my problem i think is solved, thank you for trying to help.
@odoo, @odoo_team
i cant delete my own mistake comment and answer to other reply, because CarmaError.
Can it be available for default?