Logic Flow Connector
Planner entities (Boards/Tasks) should act both as a trigger as well as an action recipient of Logic Flow as well as Azure Logic Apps. This way we can enable workflows integrating with external SaS apps (VSTS the obvious candidate) as well as internally within O365.
Trigger examples: when a Task is closed, when a Task is (re)assigned, when a Task moved to another Bucket, when a Task is created.
Action examples: create a Task, add comment/attachment, move to another Bucket, change Task priority/assignee (or more according to the Roadmap) - essentially whatever can be surfaced through the graph task api.
shoeb khan commented
BEST MBA COLLEGE WITH LOW FESS!
Solar Panel commented
This is interesting to note and with the example it is even more easier to get.
I would like to trigger a progress status change when moving task to a different bucket.
Andy Ladwig commented
We have been trying to do this with Flow, but the Planner connector does not have any triggers. The nice thing about tasks is that its not tied to an instance of VSTS, which makes it suitable for managing projects that span multiple repositories, projects, teams, etc.. As a clunky workaround, you can create a recurrence trigger to look for new tasks, updates, etc. and act accordingly based off of that.
Allow for easy addition to a SharePoint Library home page as a Web Part