-
-
Notifications
You must be signed in to change notification settings - Fork 147
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix org name restriction, reference organization while starting timer. #2966
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks good just two changes requested
Thanks for the review |
@DonnieBLT I have done the changes you mentioned Here is the demo video: Recording.2024-11-24.125647.mp4 |
e2529fd
to
ad71fd2
Compare
can you squash the migrations please |
and maybe take out the prints |
86f4d68
to
79ed3f6
Compare
Hey, @DonnieBLT Let me know if any other change is necessary 👍 |
078a399
to
355ab1e
Compare
Thanks for the much needed assistance @DonnieBLT ! |
This is a PR in reference to issue 2851.
The bug inducing check of needing to match org name and domain name is removed with this PR.
Fixes #2851
Also the user can now optionally reference an org they want to allocate the current sizzle timelog towards with the help of the organization URL.
Right now, only the user who created the timer can see which organization they allocated their time logs.