Introduction

This blog post is part of a series discussing Microsoft Planner’s App-Powered Task feature.

• Post One: Introduction to App-Powered Tasks
• Post Two: How to Build Planner App-Powered Tasks.
• Post Three: Gotchas, Findings, Thoughts and Bugs. [This Article]
• Post Four: Features I would like to see in App-Powered Tasks.

In this blog post, I wanted to highlight some of the fun and games that I had working with Microsoft Planner App-Powered tasks.

I have seen the following issues. In this blog post, I highlight some of the problems that I have. I am sure that some of the issues, which are bugs, will get fixed as we get closer to GA:

• If you complete a task, it requires a refresh of the plan for the user interface to pick up the change and show the task as completed.
• Accessing completed tasks from the Teams Activity feed can bypass the App Powered Tasks.
• When you delete the Teams App, it will disable the Task Powered App interface, which, to be honest, all makes sense.
• Creating the various staging URLs and deep link URLs is tricky. Please use my examples to help you get it right.
• Do not use a # symbol in your external IDs, as they cause issues with the encoding and decoding of URLs. In particular,r they break the link for Teams stage links. The outcome is that the staging dialog does not appear, and you are taken into the web instance of Microsoft Teams.
• When developing a solution, use a Dev and environment-specific plan because your tasks are going to point to your development/environment Teams app.
• The Planner task may miss the start button and app task-powered element if a user is on the planner and immediately opens the task.

These issues seem to have been fixed:

• The app-powered task user interface does not always show.
• Immediately created tasks often miss the buttons and app-powered task features.
• Accessing tasks from Teams Activity can sometimes bypass the App Powered Tasks.

I am sure these issues will get resolved as the solution gets closer to release. My original development issues are getting fixed, which is great news. However, I wanted to highlight the things that I am seeing, and I will feed them back to Microsoft.

Conclusion

This post highlighted some issues that I have seen with Planner App Powered tasks. However, I can already see that some of these issues that I originally flagged have been resolved. This is great news, and I hope is a sign that the solution is coming towards being ready for general availability 🙂