Custom workflow support #12
Merged
Conversation
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Issue
https://www.wrike.com/open.htm?id=696166641
Closes #11
What
Handle custom workflows
Why
Any bigger org probably uses custom workflows that they tweak to their needs.
Without this support on merge of a PR the task is forcefully moved to the default workflow, instead of what's set up for its folder.
How
There is no notion for what's the "appropriate" next status for a task in wrike's API, so on merge of a Pull Request wrike-ist will update the status of the linked task to the first Completed status in the task's workflow.
This works with the default workflow as well (used in free accounts).