Groups

Business context:
A logged in user should be able to see groups created by him/her + groups in which s/he is a member

As a logged in user, I should be able to view all my groups, So that I can perform various actions within the group

Acceptance criteria:

Pre-conditions:
Logged in user has clicked the option to view all groups

Verify that:

User is able to view all groups where s/he is admin (group can be created by him/her or assigned to him/her )
User is able to view all groups in which s/he is a member
A group has a special indication if s/he is the Admin of that group (group creator or assigned as admin)
All the groups where s/he is an admin is shown first, followed by groups that s/he is part of
Groups are ordered by creation date - recent to last (within admin & non-admin sections)
User sees an option to create a group

Form Configs Associated:

Master Component List

Following are the list of components required to be re-used across Mobile & Portal :
Please refer to following link for CC
https://github.com/Sunbird-Ed/SunbirdEd-consumption-ngcomponents/

Plugin/Component	Plugin Invocation	MetaData	PluginType
Course	`<sb-course-card [content]={{?}} (cardClick)="cardClick($event)" (menuClick)="cardMenuClick($event)"><sb-course-card>`	{}	Card
Announcement	`<sb-announcement-card [content]={{?}} (cardClick)="cardClick($event)" (menuClick)="cardMenuClick($event)"><sb-announcement-card>`	{}	View Only-Card
Chat	<sb-chat-room [chatRoomId]={{?}}></sb-chat-room>	{}	Module
Discussion Board	<sb-discussion-board boardId={{?}}></sb-discussion-board>	{}	Module
Text Book	`<sb-library-card [content]={{?}} (cardClick)="cardClick($event)" (menuClick)="cardMenuClick($event)"><sb-library-card>`	{}	Card
Content	`<sb-content-card [content]={{?}} (cardClick)="cardClick($event)" (menuClick)="cardMenuClick($event)"><sb-content-card>`	{}	Card
Collection	`<sb-collection-card [content]={{?}} (cardClick)="cardClick($event)" (menuClick)="cardMenuClick($event)"><sb-collection-card>`	{}	Card

Creation Form Config

Any Form Configs associated with the config will completely gets driven by backend metdata to associate forms. There is a generic Abstracted Library being built called as SB-forms. Please refer the link below:

Type	Config
AnnouncementCreate	{formName:””,fields:[{TextBox},{TextArea},{CheckBox},{Submit}]}
ChatCreate	{formName:””,fields:[{TextBox},{TextArea},{CheckBox},{Submit}]}
Discussion BoardCreate	{formName:””,fields:[formName:””,{TextBox},{TextArea},{CheckBox},{Submit}]}
….

Element Config

Drop Down Config

{
  "code": "category",
  "type": "select",
  "default": "loginRegistraction",
  "templateOptions": {
    "placeHolder": "Select Category",
    "multiple": false,
    "hidden": true,
    "dataSource": DATASOURCETYPE.LOCAL || DATASOURCE.CLOSURE || DATASOURCE.API
    "options": CLOSURE || INDEPENDENT SERVICE CALL || [
      {
        "value": "content",
        "label": "Content"
      },
      {
        "value": "loginRegistraction",
        "label": "Login/Registration"
      },
      {
        "value": "teacherTraining",
        "label": "Teacher Training"
      },
      {
        "value": "otherissues",
        "label": "Other Issues"
      }
    ]
  }
}