JSellers0 / JSellers0/PythonTimeClock_Flask_WebApp
Site timeout causes issues with reported hours
Open
Nobody has claimed this yet.
bug
- Dominant language
- Python
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Site times out. When logged back in, there is no way to continue the previous timelog row.
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
No files or tests are named. Start by reproducing the site timeout and checking how the timelog row is persisted across logout and login; done means a user can continue the previous timelog row after reconnecting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- flask, python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100