![]() ![]() I use planner to create a KanBan board to my team for a DevOps approach for application releases, as I have multiple buckets, the percentage wasn’t enough, so I took the idea and expanded a bit using a excel spreadsheet and I wanted to share the knowledge. Great post Rudy, thanks for sharing this content! Sometimes by thinking a bit out of the box, we can still automate our tasks, we just need to take a look at it from another angle. Also, the platform is still growing and new connections, triggers and actions are added regularly we still miss some basic actions or triggers in it. ![]() Microsoft Flow is a great tool to automate things. Set the task id (just scroll down to Enter Custom value) and the progress value to In Progress This way we know that this task is processed when the flow runs again. The last action in If Yes is to set the percentage to 50. If you need the task description (and you probably do), you can add the Planner action, get task details first. I leave the details out of this article, check this article if you want to know more about it. In the If Yes part we add the action create Issue. So we are going to create a GitHub issue from it. If the percentage is 0 we have a new task for this bucket. Check the Percentage Complete value, it has to be equal to 0. Add a condition below the Get a task action. Now we need another condition, we are going to check the task progress. Link the task Id by using the Value Id field Add an action in the If Yes part and select the Planner action get a task. Not the task details, because that will only return the description. If the task is in the correct bucket we are going to get the task. We are going to check the value Bucket Id and it has to be equal to the bucket Id that we found in Planner or Graph. Select the condition action from the built-in actions. Select the output Value from the previous step.Īdd an action in the apply to each. Add a new step and select the built-in action apply to each. Next, we want to loop through all the task in the list. Set it to an interval of 10 minutes or whatever works for you.Ĭreate a new step and select the List tasks action from Planner If so we create an issue in GitHub and set the progress to 50%. For each task, we check if it’s in the correct bucket and if the progress is on 0%. In the Flow, we will get all the task for a plan. Instead of focusing on the task moved action I decided to run a Flow every 10 minutes. After some testing, I came up with a solution that works quite well. We need to find a way to check if a task is moved to another bucket and create a GitHub issue when it’s. You can post ideas or suggestion on the Microsoft PowerUser forum and this one is also listed there for more than a year. The only triggers available in Flow for Planner are:Īnd what we really need is the trigger, when a task is moved. So sometimes we really mis a feature we need, just like this one. We can’t create our own triggers or actions. The connector and there triggers and actions in Microsoft Flow are create by Microsoft self. So the trigger in Microsoft Flow is when a Planner task is moved. We wanted to create a Github issue when a task is moved from the backlog to the sprint backlog. Our development team is growing and they are using Planner as there KanBan board. This is working fine for the project I am working on, but we needed more for our web development team. I have written before about how I using Microsoft Flow to automatically create GitHub Issues from tasks in Planner. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |