magello-group / magello-group/evoAppen

TODO

Open
#1 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Description

**High Priority:**

- [ ] Add Template (don't forget to store userId of template maker so he/she can edit)
- [ ] Edit Round (use same component as new-round, check for edit param from useRoutes and do a fetch)
- [x] Delete Round (Have delete option in table drop down)
- [x] Mandatory motivations are not set properly when creating round
- [ ] Rename pages and components to consistent convention (PascalCase)
- [ ] In EditRound, the description is hardcoded and not from apiData.

**Medium Priority:**

- [ ] Add names of authenticated users in landing page table. If a konsultchef wants to find specific employees' rounds, it should be possible, maybe even searchable.
- [ ] Clean Up old ToDo infra and code
- [ ] Check for Type mismatch between FE and API
- [ ] Stop user from accidentally leaving the page when filling out editRound form. Maybe use "beforeunload"
- [ ] Color Schemes for user answers and Score colors
- [ ] Button to add link to clipboard
- [ ] Dropdown in landing page table has dead spots. You now have to press in the middle of option

**Low Priority:**

- [ ] Create "Om evoAppen" dialog and text
- [ ] Table for My Templates (to edit and remove templates)
- [ ] Have a maximum answers option
- [x] Dropdown option in SpiderChart to get mean value of all users combined.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No specific file or test is named. Begin by separating the unchecked items into individual tasks and inspect the new-round/EditRound components, landing page table, SpiderChart, and the frontend/API boundary mentioned in the checklist. Each task is done only when its own behavior and acceptance criteria are defined and verified.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
full-stack
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.