Add feature to optionally set iteration

[heresandyboy]

Hi,

My team and I came across your plugin recently. We started to use it but realised that it was hard coded to only show User Stories in the current iteration. We typically plan out tasks in refinement for the next iteration and found we couldn't use this awesome plugin for that.

I decided to have a look over the code and see if I could implement a feature to enable us to set the iteration, in the same way you select user stories.

Here is my pull request containing the feature to set the iteration for the plan.

I have used the prefix IT# which will lookup the iterations for the team. The iteration Guid is set as the id. The iteration must be set on line 0.

The user stories are then retrieved using that iteration id. You don't have to specify the iteration. If you don't include iteration syntax in the file then it will just default to the currentIteration, working the same way you had it before.

Please review this code and let me know if you are happy, if you want to make any changes to my fork / feature branch then feel free.

Many thanks,

Andy

EDIT: fix typos

[ipatalas]

All right.. I think I have just resolved the conflicts :)

[heresandyboy]

Thanks for your kind feedback and for merging your latest in for me! This is literally my first PR on a public repo, and the first time I've seen any VSCode plugin source code! I really enjoyed taking it for a spin. I totally agree about the guids, I haven't been able to think of a better way, besides perhaps parsing the full path and doing a lookup using that. I'll push the changes as requested shortly.

You know, it was just some lucky google searching that led us to this plugin, I'm leading the push for our company to adopt Azure DevOps at the moment. The first team to use it in sprints gave some feedback that planning/refinement sessions were taking longer than previously, thanks to having to click around filling in form after form. I was literally thinking wouldn't it be nice if there was a plugin for VSCode that would let us more easily create tasks and so on. I eventually googled 'VSCode azure devops planning' and you were the top result.

Our team has started using my forked plugin during sprint ceremonies (by actually debugging my branch in VSCode). They are looking forward the the request being merged and potentially contributing features to the plugin in the future.

I see you added a mini roadmap, we have discussed how it might be useful for us to be able to create Stories or create Bugs\add tasks to existing bugs from the plugin (we track Bugs with requirements and tasks in the Sprint).

Along the lines of US* New user story title or BG: New bug title Any character pattern will do I guess, like BG~ New bug title or US+ New story Actually I think the '+' would be quite intuitive.

I'd be interested in your thoughts and I look forward to potentially contributing further in the future .

Thanks for making such a simple to use but incredibly useful plugin!

[ipatalas]

This is literally my first PR on a public repo, and the first time I've seen any VSCode plugin source code! I really enjoyed taking it for a spin.

Yeah, it's so easy and fun to do :)

I totally agree about the guids, I haven't been able to think of a better way, besides perhaps parsing the full path and doing a lookup using that.

I think using just the human readable name instead of GUID, so Sprint 43 or the full iteration path. It's more clear for the user and then map it to a GUID under the hood but that's an enhancement that can wait.

You know, it was just some lucky google searching that led us to this plugin, I'm leading the push for our company to adopt Azure DevOps at the moment. The first team to use it in sprints gave some feedback that planning/refinement sessions were taking longer than previously, thanks to having to click around filling in form after form. I was literally thinking wouldn't it be nice if there was a plugin for VSCode that would let us more easily create tasks and so on. I eventually googled 'VSCode azure devops planning' and you were the top result.

Nice story :) I never realized people google for extensions instead of searching via marketplace. That might make sense though. Google index is probably just better.

Our team has started using my forked plugin during sprint ceremonies (by actually debugging my branch in VSCode). They are looking forward the the request being merged and potentially contributing features to the plugin in the future.

Looks like you were desperate to use it :) I'll try to publish new version this evening to make it easier :)

I see you added a mini roadmap, we have discussed how it might be useful for us to be able to create Stories or create Bugs\add tasks to existing bugs from the plugin (we track Bugs with requirements and tasks in the Sprint).

Along the lines of *US New user story title or BG: New bug title Any character pattern will do I guess, like BG~ New bug title or US+ New story** Actually I think the '+' would be quite intuitive.

Altought we have user stories prepared by our BAs upfront of the sprint so we don't have to add them manually that make sense in general. I like the idea. + seems a good option for new item.

I'd be interested in your thoughts and I look forward to potentially contributing further in the future .

That would be great. I'm open to new ideas and I can't handle it all alone. The only danger is that every team works differently so it's better to discuss the idea first to make it as backwards compatible as possible so that we can still use it in our project :)

Thanks for making such a simple to use but incredibly useful plugin!

Credit goes to @mbiernacik for bringing the idea. I just made the it real.