[Bug Report]: Unable to add a totally new Location it has to be part of another location.

[madrinekariuki]

Affected Project

ECBIS

How to replicate

web version: v3.1.2
user: ecbis

Issue:
On the location management, one is unable to add a totally new location, you can only add a location unit that is part of an existing location.

Steps:

• login to webUI
• click on location management.
• click on location units.
• click on Add a location unit.
• try to add a new location unit
• observe that you can only add a location unit that is part of an existing location, a new location cannot be added.

Acceptance criteria

• One should be able to add a new location in the location units.

Project Contact

No response

Relevant Information

[peterMuriuki]

@madrinekariuki I think there is some conflicting language that confuses me. Is the issue that:

1. Click on add location -> fill in the name field only(this would create a parent location) -> and save, that this does not work.
2. or if you select a value in the part of field, you cannot unselect it.

When you say a new location cannot be added. What's the manifest of this, is there an error that you observed, in what way did the app behave that did not match your expectations

[madrinekariuki]

@peterMuriuki
using below screenshot, we have 2 locations, Test B and Liberia, when you want to add another location e.g Test C, and you click on Add location Unit, You will observe that you can only add a location that is part of an existing location i.e test B or Liberia but you cannot add a new location.

[peterMuriuki]

@madrinekariuki if you only fill in the location name, and save, this should create a location at the same level as testB and Liberia is this not what is happening?

[peterMuriuki]

@madrinekariuki what did you find, should I close this?

[madrinekariuki]

@peterMuriuki This action is overwriting current existing locations. see below Test B and Liberia are now missing cc @AnnieMungai

[peterMuriuki]

@madrinekariuki I believe this can be categorized as a different issue, and will track as part of #1288