ita-social-projects / ita-social-projects/SpaceToStudy-Client
SpaceToStudy: Epic list
- Dominant language
- TypeScript
- Stars
- 24
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
№ | Epic | Link
--|--|--
1 | Home page | #4
2 | Header/Footer | #12
3 | Error messages | #13
4 | Admin | #5
5 | Sign in/Sign up | #6
6 | Mentor cabinet | #7
7 | Student cabinet | #8
8 | Mentor profile | #9
9 | Student profile | #10
10 | Categories | #11
11 | Chat | #1376
12 | | #
13 | | #
14 | | #
15 | | #
16 | | #
17 | | #
18 | | #
Epic and user story management system rules:
1. User story cannot be present in two or more epics. Each user story is present only in one epic.
2. Each user story should be linked to one of the epics after creation. If there are no epics related to user story according to described in the user story features, then new epic should be created and added to the common epic list.
3. Labels which should be added to epic after creation: "Epic", "", "" (if any). If there are no separate features in the created epic, then feature labels should not be created.
4. Labels which should be added to user story after creation: "User story", "", "" (if any).
Contributor guide
Research direction
Review the epic list and the stated rules for linking epics, user stories, and labels. The issue does not name files, tests, or a specific change; clarify the intended update before work begins, and consider the list and rules complete only once the requested epic and label relationships are explicit.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100