openwisp / openwisp/openwisp-controller
[bug] Changing location organization does not change the floorplan organization
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 773
- Forks
- 315
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 14
Description
While registering a new floorplan, there is no choice to select the organization, which infers that it should be the same as the location.
After creating a location (Let's say location_a for organization_a), if we create a floorplan, its organization will also be organization_a
However, if the organization of location is changed (for example, to organization_b) the floorplan will still have the old organization
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how a location's organization is updated and how its floorplan organization is stored. Reproduce the described sequence with location_a, organization_a, and organization_b; this is done when changing the location organization also updates the associated floorplan organization.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- django, python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100