Parent field name should always match parent entity type. Can then remove "parent_field_name" and "query_string" from tests
The query string for parent should be uniform, and have two keys:
- parent_field=<machine_name_of_base_field_to_populate>
- parent_id
Parent field name should always match parent entity type. Can then remove "parent_field_name" and "query_string" from tests
organisation relations (although they will become customer relations)
They can go in config/install and then be edited for different clients
- [ ] cases
- [ ] activities by customer
- [ ] activities by case
- [ ] case provisions
- [ ] case fees
- [ ] organisation relations (although they will become customer relations)
They can go in config/install and then be edited for different clients
All should have view and edit links (view can be removed if the entity is small but that depends on the client) and no column should be linked to the entity, only to other entities e.g. provider field in case provider
All should have view and edit links (view can be removed if the entity is small but that depends on the client) and no column should be linked to the entity, only to other entities e.g. provider field in case provider
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The query string for parent should be uniform, and have two keys:
Parent field name should always match parent entity type. Can then remove "parent_field_name" and "query_string" from tests
cases
activities by customer
activities by case
case provisions
case fees
organisation relations (although they will become customer relations)
They can go in config/install and then be edited for different clients
All should have view and edit links (view can be removed if the entity is small but that depends on the client) and no column should be linked to the entity, only to other entities e.g. provider field in case provider