Azure DevOps planner
This extension features ability to export a planning session into Azure DevOps system. Planning in Azure DevOps itself is hard, way too much clicking. It's so much easier to just type all the tasks in a simple text form and then just export them.
To start a planning session open a new file in vscode and change the language to
Before you can start you have to configure connection to your Azure DevOps account. For that you will need a URL and a token for authentication. For details please check the Configuration.
Now it's time to start planning your first story. You can start by typing
If you wish to add tasks for iteration other than current you can do so by choosing it at the beginning of the file:
Then it's time to enter some tasks in the following manner:
he image should be pretty self-explanatory I hope. The numbers following the tasks are estimations. They will be filled in both Original and Remaining Estimation field in Azure DevOps. As you can see it can be specified in both hours (up to 2 decimal places) and minutes (integer).
At this point there is a Code Lens action above the user story that lets you publish the changes. Check it out. In case of something is not working just open Output panel and pick
Since 0.3.0 tasks can be updated. After a publish all published tasks should get their ID instered at the end of task line. Don't play with those IDs if you don't want to make a mess. Later on you can change the title or estimation and such task will get updated next time this User Story is published.
Creating User Stories
Apart from creating tasks you can now also create new user stories. Just use the snippet
After publishing you will get User Story ID filled and you can add more tasks then or update existing ones:
This extension contributes the following settings:
To change the settings please use
For the token to work correctly it only needs one single scope: Work Items (read & write)
It's often the case that some tasks repeat among all or almost all user stories. There is no need to type them all manually every time. It's a tedious task and should be automated. For instance we have automated tests. Additionally we do so called triangle meetings (BA/DEV/TEST) before starting the story to make sure we understand it correctly and also a short test pyramid meeting to preselect which tests go where (unit, integration, ui). Given that activities we have 6 common tasks (actually it's even more but you get the point) that we should add to every single User Story on planning session. We never liked adding that manually.
Let's handle this like a pro! Go to settings file (UI doesn't provide option to define this yet) so
The format of the file is as in the example: https://gist.github.com/ipatalas/8bb7b2fdb2e1c26dc8249659791cf56e#file-taxes
It will be read only once when activating the extension (usually first time you open a
Isn't it better than you used to do it?
I am using another extension to make it easier to change the estimations:
There are few similar extensions available on the market. I picked Incrementor.
VSCode allows you to bind any commands to a key so I bound increment/decrement to