In principle I agree with removing the dependency, but did you confirm the impact in the workflow?
It's because crm.claim provided a lot of logic for state changes, and it's possible that some behaviours rely on that dependency.
PS:
An idea to explore in a later MP is to add stages to the NCs and create a Kanban view. ideally it should work in a way very similar to Project Tasks or Issues.
In principle I agree with removing the dependency, but did you confirm the impact in the workflow?
It's because crm.claim provided a lot of logic for state changes, and it's possible that some behaviours rely on that dependency.
PS:
An idea to explore in a later MP is to add stages to the NCs and create a Kanban view. ideally it should work in a way very similar to Project Tasks or Issues.