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
Allow moving integration tasks between teams #5513
Merged
mattkrick
merged 15 commits into
master
from
feat/5200/allow-moving-teams-of-integration-tasks
Nov 11, 2021
Merged
Changes from 2 commits
Commits
Show all changes
15 commits
Select commit
Hold shift + click to select a range
81ef6b2
Allow moving integration tasks between teams
Dschoordsch 0847523
Remove teamId from updateTask mutation
Dschoordsch 9b28d90
Merge branch 'master' into feat/5200/allow-moving-teams-of-integratio…
Dschoordsch e5f7267
Before moving a task to another team check if an integration is needed
Dschoordsch 952ee95
Fix TaskFooterTeamAssigneeMenu_task fragment
Dschoordsch 10b24cf
Show add integration dialog when moving task to team w/o integration
Dschoordsch 6973960
Polish add integration now dialog
Dschoordsch 7921814
Merge branch 'master' into feat/5200/allow-moving-teams-of-integratio…
mattkrick 5fa6716
Merge branch 'master' into feat/5200/allow-moving-teams-of-integratio…
mattkrick cc7d172
Cleanup
Dschoordsch aaa72be
Copy integration first before moving a task to a different team
Dschoordsch 5266696
Don't start OAuth flow when moving a to another team w/o integration
Dschoordsch 6cf7590
Cleanup
Dschoordsch be84ae2
Merge branch 'master' into feat/5200/allow-moving-teams-of-integratio…
Dschoordsch d73485b
Clear freshly added integration auth from dataLoader
Dschoordsch File filter
Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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's possible that someone calls this mutation outside of our UI.
If that happens, we need this mutation to guarantee that an integration exists on the new
teamId
I propose the following:
eliminating the extra oauth2 flow means the process goes faster & more importantly we can verify that the new teamId supports that task integration
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.
I got a bit lost in edge cases. When the viewer has no integration in the target team, there are these options:
For now I ignore 2) and 3) and just assume it's 1) as that's the most common case in the UI.
Better would be of course to detect 2) and 3) as well and handle it appropriately in the UI, but we do not get all information necessary at the moment via GraphQL and I also don't want to repeat the same logic if there is a nicer solution.
Let's just roll with 1) and fix 2) and 3) another day, user value is probably also minimal. Use case 2) I can imagine is a bit annoying, i.e. team lead has 2 parabol teams and adds integration. They're also the only ones with access to Jira. Every time some other team member would move a task, they would get shown the dialog. It would still move the task, but it might get annoying. But if that hypothetical user exists, they can open a ticket.
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.
fantastic work exploring all the edge cases.
i think your assumption are reasonable & i feel very comfortable with the solution you've built!