Group Level Wiki: FE BE Search functionality
Problem to solve
Note: This issue is a child of the Group Level Wiki Implementation Epic &2214 (closed)
TBD
Proposal
TBD
UX Screens needed (Remove if not needed)
-
Screen 1 -
Screen 2
Dependencies (remove if not applicable)
This issue cannot be started until the following issues have been merged:
Issue - 1
Issue - 2
Issue - 3
Assumptions (remove if not applicable)
The following assumptions are being made:
Assumption - 1
Assumption - 2
Assumption - 3
Tentative MR Breakdown
The following are potential options for how to break this down into multiple MRs
MR Title - 1
MR Title - 2
MR Title - 3
(This is just a guideline, as an Engineer, you always have flexibility with your implementation approach)
Intended users
There are over 600 upvotes on the original issue. Users of any persona who have access at the Group Level can use and create a wiki. System Administrators and Company Leaders most want to share information across projects.
Permissions and Security
Role-Based Access Control (RBAC)
RBAC restricts access based on a person's role. Should any Role-Based Access Controls be reviewed or added based on this issue? Yes/No
Permission Based Access Control
Permission Based Access Control determines the type of access allowed (e.g: Read, Write, Delete, etc). Should any Permission Based Access Controls be reviewed or added based on this issue? Yes/No
More Authentication and Authorization
Documentation (remove if not applicable)
This issue does / does not
require the creation of documentation.
- If this issue requires the creation of documentation, add documentation
Testing
Testing Approach
By taking just a little extra time in our test approach to think about testing in general, we can save hours of work rolling back a release or producing hotfixes. A few areas to consider are boundaries, configuration settings, counts, CRUD,Depth,Soap Operas and Extreme Personalities. More can be found here.
- Testing for
TBD
- Testing for
TBD
- Testing for
TBD
- Testing for
TBD
- Testing for
TBD
- Testing for
TBD
Success Criteria
-
Success Criteria 1 -
Success Criteria 2 -
Success Criteria 3 -
Testing Related Success Criteria (remove if not applicable) -
Security Related Success Criteria (remove if not applicable) -
Documentation has been written or updated (remove if not applicable) -
Unit Tests have been written -
Integration Tests have been written (remove if not applicable) -
End to End Tests have been written (remove if not applicable)