Skip to content
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

Assigned users are still lost when editing a project #145

Open
kralan opened this issue Oct 1, 2021 · 4 comments
Open

Assigned users are still lost when editing a project #145

kralan opened this issue Oct 1, 2021 · 4 comments

Comments

@kralan
Copy link

kralan commented Oct 1, 2021

#121 appears to have been closed prematurely.
Only the part of the problem split out as #144 is solved.

The original problem as reported by @AlexandersWebdesign and detailed by @Eothred persists:

  • when editing a project the list of allowed users is cleared (this may be intended or not)
  • when the list of allowed users is empty, the project cannot be used by any user, be it locked or not (this most probably is not intended)
@aq18507
Copy link

aq18507 commented Oct 5, 2021

I am experiencing the same issue. The problem is not only that the user is cleared but also that the it can no longer be added again to the project.

@sebix
Copy link

sebix commented Feb 4, 2022

Only for experienced users!

To work around this bug I directly re-added the user in the DB.

  • In the UI go to the Projects page. Identify which project (name, not ID) is missing the user-attribution.
  • Using select * from oc_timetracker_project; identify the project ID and optionally the created_at values by the name.
  • Add the user with insert into oc_timetracker_user_to_project (`id`, `user_uid`, `project_id`, `admin`, `access`, `created_at`) VALUES ($free_id, "$user_uid", $projid, 1, 1, $created_at); with the corresponding values replaced. In my case the oc_timetracker_user_to_project IDs 1:1 corresponded to the project IDs, this may vary in your case. Make sure to not mix up with the auto increment ;)

@dbeniamine
Copy link

I have the same issue, since upgrade to NC 23 ...

I hope it will be fixed, because this tool is quite useful !

@dbfischer
Copy link

This issue is still unresolved in the 0.0.74 release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants