What?
A non-pillar user has to switch the selected address to see projects on another address. While a pillar user sees all projects for all addresses.
Example
An user with 3 addresses
Address 1 has a pillar registration and 3 projects
Address 2 has 1 project
Address 3 has 1 project
- When address 1 is selected, the user sees all 5 projects when activating the ‘My projects’ filter tag.
- When address 2 or 3 is selected, the user only sees project 1 when activating the ‘My projects’ filter tag.
Why?
When address 1 is selected the user is considerd a pillar user, otherwise a non-pillar user.
The ‘My projects’ filter tag, filters on all user addresses, but as a non-pillar owner the result set gets filtert down in the _filterProjectsAccordingToPillarInfo function to all active projects or projects owned by the selected address.
How?
With the following change the situation would be equal to that of a pillar user and the user would not have to change the selected address to see all his owned projects.
This above solution brings non-pillar users in line with pillar users, but eventually one does need to switch to the owned address when creating phases. This applies to both non-pillar and pillar users. This could be a bit confusing when someone is not familiar with the concept. The “create phase” will only be visible when the address of the project owner is selected.
Pros
- Allows the user to see all projects without the need to switch.
Cons
- Confusing when creating phases
Alternative solution
Bring pillar users in line with non-pillar users. Both user types only see “my projects” that match the current selected address.
Implementation
https://github.com/KingGorrin/syrius/tree/az-projects-filter