You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Allow user's to create or subscribe to public brains in order to share knowledge without having to share a specific link.
The what
What are we developing?
Separate private brains (ones that can be shared to others via an invitation) from public brains (can be subscribed to from the brains market place)
What are the validation criteria to validate this feature?
What are you going to test to validate this feature? What are the edge cases? How should the feature behave in case of error ? How should the feature behave in case of missing data ? Are there other specific behaviours that should be clarified?
THE WHAT. V2
a) AAUser, I can create public brains :
-When I click on « create new brain », I can see a dropdown menu « type of brain » which is automatically set on private brain (this section exists on the setting page as well). I can select « public ». But if I click on public, I have a popup « … ». I can close this popup with the cross. If I change the brains type, the new type will then be selected in the dropdown menu.
If I set my brain on public, every Quiver user can subscribe to it in the « brain library »
b) AAUser I can see that a brain is public :
On the settings page with a tag « public ».
All the settings are not editable when it’s public, I can only see the information in « hard ».
There is no « people » and « knowledge » tab
On the left modals « list of brains » with a badge « public » next to the different brains names.
a) AAUser, I can access a public brains library from the brain management page + AAUser, I can use a searchbar to find a brain
2-b AAUser, I can see the list of public brains with the beginning of description
2-c AAUser, when I click on a brain, I can see a pop up with the complete brain info, I can add this brain or click on the cross to close the pop up
3- AAUser, I can subscribe to a public brain by clicking on « subscribe »
Once I subscribed to a brain :
The label is changed from « subscribe + » to « subscribed »
I can see a badge « 1 » next to the brain on the nav bar for a few seconds.
The brain is in grey
AAUser, I can unsubscribe from a brain : -In the settings section, instead of the « delete brain »
AAUser, I can set my brain on private after setting it on public.
-The brain won’t be in the brain library section anymore
-Every users who subscribed to this brain won’t have access to it anymore. They will see in the left list the name of the brain with an icon « warning ». If they click on the brain they will see « This brain is no longer available to the public ». In the chat, they will see a warning icon next to the brain that as been set back on private. And the brain won’t be clickable anymore.
THE WHAT V1 (OLD)
a) AAUser I can see that a brain is public :
On the settings page with a tag « public ».
All the settings are not editable when it’s public, I can only see the information in « hard ».
There is no « people » and « knowledge » tab
On the left modals « list of brains » with a badge « p » next to the different brains names.
b) AAUser, I can create public brains :
-When I click on « create new brain », I can see a dropdown menu « type of brain » which is automatically set on private brain. I can select « public ». But if I click on public, I have a popup « … ». I can close this popup with the cross. If I change the brains type, the new type will then be selected in the dropdown menu.
a) AAUser, I can access a public brains library from the brain management page
Img
2-b AAUser, I can see the list of public brains with the beginning of description
2-c AAUser, when I click on a brain, I can see a pop up with the complete brain info, I can add this brain or click on the cross to close the pop up
3 - AAUser, I can subscribe to a public brain by clicking on « subscribe »
Once I subscribed to a brain :
The label is changed from « subscribe + » to « subscribed »
I can see a badge « 1 » next to the brain on the nav bar for a few seconds.
The brain is in grey
AAUser, I can unsubscribe from a brain :
-In the settings section, "Unsubscribe from brain" instead of the « delete brain »
AAUser, I can set my brain on private after setting it on public
In settings tab add a switch to manage access
Remove public from settings tab
BE: Update backend
Access to library
SEARCH
I can search for brains, by using the search bar.
SUBSCRIBE
What’s out of scope for this feature?
Should this feature be feature flagged?
The how
How are we going to code this feature?
What’s the technical strategy to deliver? What are the impacts on the architecture diagram? What could be the unexpected consequences of the feature on other parts of the code? Could there be other technical edge cases?
Are there any technical decisions made that should be shared?
Did you make any ADR for this feature that should be shared and validated?
What is preventing us from delivering this feature?
Are there functional dependencies? Are there métier dependencies? Are there internal teams that need to be consulted/need to validate
What can the feature potentially break?
The text was updated successfully, but these errors were encountered:
The why
Allow user's to create or subscribe to public brains in order to share knowledge without having to share a specific link.
The what
What are we developing?
Separate private brains (ones that can be shared to others via an invitation) from public brains (can be subscribed to from the brains market place)
What are the validation criteria to validate this feature?
What are you going to test to validate this feature? What are the edge cases? How should the feature behave in case of error ? How should the feature behave in case of missing data ? Are there other specific behaviours that should be clarified?
THE WHAT. V2
-When I click on « create new brain », I can see a dropdown menu « type of brain » which is automatically set on private brain (this section exists on the setting page as well). I can select « public ». But if I click on public, I have a popup « … ». I can close this popup with the cross. If I change the brains type, the new type will then be selected in the dropdown menu.
If I set my brain on public, every Quiver user can subscribe to it in the « brain library »
2-b AAUser, I can see the list of public brains with the beginning of description
2-c AAUser, when I click on a brain, I can see a pop up with the complete brain info, I can add this brain or click on the cross to close the pop up
3- AAUser, I can subscribe to a public brain by clicking on « subscribe »
Once I subscribed to a brain :
-The brain won’t be in the brain library section anymore
-Every users who subscribed to this brain won’t have access to it anymore. They will see in the left list the name of the brain with an icon « warning ». If they click on the brain they will see « This brain is no longer available to the public ». In the chat, they will see a warning icon next to the brain that as been set back on private. And the brain won’t be clickable anymore.
THE WHAT V1 (OLD)
-When I click on « create new brain », I can see a dropdown menu « type of brain » which is automatically set on private brain. I can select « public ». But if I click on public, I have a popup « … ». I can close this popup with the cross. If I change the brains type, the new type will then be selected in the dropdown menu.
Img
2-b AAUser, I can see the list of public brains with the beginning of description
2-c AAUser, when I click on a brain, I can see a pop up with the complete brain info, I can add this brain or click on the cross to close the pop up
3 - AAUser, I can subscribe to a public brain by clicking on « subscribe »
Once I subscribed to a brain :
AAUser, I can unsubscribe from a brain :
-In the settings section, "Unsubscribe from brain" instead of the « delete brain »
AAUser, I can set my brain on private after setting it on public
Access to library
SEARCH
I can search for brains, by using the search bar.
SUBSCRIBE
What’s out of scope for this feature?
Should this feature be feature flagged?
The how
How are we going to code this feature?
What’s the technical strategy to deliver? What are the impacts on the architecture diagram? What could be the unexpected consequences of the feature on other parts of the code? Could there be other technical edge cases?
Are there any technical decisions made that should be shared?
Did you make any ADR for this feature that should be shared and validated?
What is preventing us from delivering this feature?
Are there functional dependencies? Are there métier dependencies? Are there internal teams that need to be consulted/need to validate
What can the feature potentially break?
The text was updated successfully, but these errors were encountered: