Organizers and Site Administrators should be able to see username history of an account
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 40/100
Research direction
The payload names no files, so begin by finding where a site administrator changes a username and where account details are shown to organizers and administrators. The change has to keep the old username when the name is replaced, which likely means a new stored field or record, and then display it in that account view. Settle the open question about whether the saved history should be locked before writing code. Done means a username change leaves a record of the previous name that organizers and administrators can see, and regular users cannot.
Written by the indexing model from the issue text.
Description
Site Administrators can change the username of an account if requested, but the old username should still be saved (but not locked?) so that it can be displayed in the history of the account for Organizers and Site Administrators.
- Dominant language
- Python
- Stars
- 181
- Forks
- 80
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 33
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from codalab/codabench
-
Wrong count for failed submissions in Resource interfacePossibly taken @ihsaan-ullah claimed this 2 days ago. OpenBug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Resource Interface: Improve time formatPossibly taken A pull request linked to this issue is open or already merged. OpenBeginner Enhancement UI
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Unused datasets cleanup counts solution datasets and deletes their solutionsPossibly taken @ihsaan-ullah claimed this 1 day ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
Discussion
Difficulty 4/5 1-2 days Newbie friendliness 25/100
codalab/codabench#2640 · 2 comments ·
Maintainers usually reply within 1 day
-
Site-wide announcementsPossibly taken @ihsaan-ullah claimed this 1 day ago. OpenEnhancement UI
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Maintainers usually reply within 1 day
All issues in codalab/codabench
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
topoteretes/cognee#5647 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Sendspin/sendspin-python-cli#291 ·
Maintainers usually reply within 6 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
awslabs/visual-asset-management-system#414 ·
Maintainers usually reply within 1 day
-
bug v1 v2
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
modelcontextprotocol/python-sdk#3670 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
aicell-lab/bioengine#232 ·
Maintainers usually reply within 1 day