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

Fix getting responsibleTasks #3266

Merged
merged 2 commits into from
Oct 27, 2020
Merged

Conversation

gjvoosten
Copy link
Collaborator

Fixes part of commit 5c8df12, which would always get the responsibleTasks for the current user doing the request, instead of those belonging to the Person object.
Move responsibleTasks to Position, as that is the proper place for it, and reflect this change in the JavaScript code requesting them.

  • anet.yml needs change
  • db needs migration
  • documentation has changed
  • graphql schema has changed

Checklist

  • Described the user behavior in PR body
  • Referenced/updated all related issues
  • commits follow a repo#issue: Title title format and these 7 rules
  • commits have a clean history, otherwise PR may be squash-merged
  • Added and/or updated unit tests
  • Added and/or updated e2e tests
  • Added and/or updated data migrations
  • Updated documentation
  • Resolved all build errors and warnings
  • Opened debt issues for anything not resolved here

Fixes part of commit 5c8df12,
which would always get the responsibleTasks for the current user doing the request,
instead of those belonging to the Person object.
Move responsibleTasks to Position, as that is the proper place for it,
and reflect this change in the JavaScript code requesting them.
Add it to Position object in case we use it
@VassilIordanov VassilIordanov merged commit 5a82765 into candidate Oct 27, 2020
@VassilIordanov VassilIordanov deleted the GH-3208-fix-responsibleTasks branch October 27, 2020 14:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants