* Bugfix provider_type on nil
* Do not infer managing org
* Always show 'your org' to non support users
* Never show created_by_id in CYA
* Show HousingProvider in CYA when not inferred
* Always show ManagingOrganisation
* Spec fix
* Show ManagingOrganisation if managing agents >=1
* typo
* Show also users from owning_organisation
* Correctly handle housing provider question
* Managing Organisation page should behave the same if user is support
* Fix feature test
* Add scopes to OrganisationRelationship
* Update seeds to have more than one org relationships
* Pass current_user to questions
* Add new questions
* Use feature flag
* Update specs
* Address comments
* Add abstract log class and sales log class
Created a parent log class for sales log and lettings log. Any bits common
to both sales and lettings can live in the parent class. As the sales log
functionality is built up any commonalities with lettings log can be extracted
into the parent log class. The sales log model is set up without a json form
and instead the form is defined in code - like the setup section of the lettings
log.
* update sales logs controller
* update lettings controller specs
* update filter method name
* update organisations controller
* use lettings method
* Add deleted tests back
* lint
Co-authored-by: Kat <katrina@madetech.com>
Co-authored-by: Kat <kosiak.katrina@gmail.com>
This renames the case_log to lettings_log as everything we've written so
far has been geared towards lettings of social housing so it makes sense to
have the name describe this. This is also a precursor to adding in stuff for
sales logs (whatever shape that takes)
Co-authored-by: James Rose <james@jbpr.net>
* added empty feature for viewing user specific organisation
* refactored contexts in features
* correctly failing feature
* code to have user link
* spec to test we are at correct sub menu for Users
* added view for users view
* edited text to pass remaining tests
* fixed hidde3n field view
* removed hidden field in the table
* correct context
* added extra field to test hidden content
* test TabNavHelper with correct property
* fixed tab highlights
* spec for sub nav logs
* spec for all sub menus
* testing users inside org
* better test for listing users
* all test for search inside org users
* pressing button
* passing feature
* better test with multiple orgs
* almost done
* fixed failing test
* rubocop
* expanded tests
* typo
* selecting subset due to null present in the list as well
Co-authored-by: Ted <ted.booton@madetech.com>
Jack S
James Rose
natdeanlewissoftwire
baarkerlounger
Dushan
Stéphane Meny
J G
JG