WorkItems linked to the Build/Release and then filter with Query about workitemupdater

[chrisevett]

Hey folks, I'm going to take a stab at this unless someone is already working on it. I have an internal ado org I'll be testing with before I send a PR

[dlmarshall3]

Hi, there! Wanted to see if there is anything we (the people who appreciate your hardwork) could do to help with this. I don't know where to begin to test locally, but something like this would be incredibly helpful to my team, where we are limited to the states we can assign our work items to. IDEALLY, having the ability to filter by Board Colum instead of State would help us immensely, but we would settle for linking to build, plus query. :) Just wish WIQL would let you query releases, pipelines, etc.

[dlmarshall3]

Good luck! Would love to see something happen here, as it'd be a huge improvement to an already helpful extension.

[gioce90]

Hi @BlueBasher , are you still supporting this project?

[BlueBasher]

Hi
Yes, I'm still supporting this project. Only have a shortage on time currently so am not able to implement any new features at this time.
If you're up for it, you could create a PR with the functionality, and I'll make sure I'll look at it ASAP.

[gioce90]

Hi @BlueBasher ,

I was wondering, in developing this task, do you have some strategy to debug the task on azure devops or do you proceed by attempts? I was trying to edit a fork, but is not clear how to debug your task on Azure Devops.
I followed these guides:
https://learn.microsoft.com/en-us/azure/devops/extend/publish/overview?view=azure-devops
https://devblogs.microsoft.com/devops/streamlining-azure-devops-extension-development/
https://github.com/microsoft/azure-devops-extension-hot-reload-and-debug
https://www.npmjs.com/package/@microsoft/generator-azure-devops-extension

[BlueBasher]

Hi, I actually proceed with attempts, and debugging by adding temporary additional logging 🙂 I've found that it's difficult to debug locally since it depends on the build-context. So I publish a private version of the extension to a sandbox DevOps organization and then run builds on that.

[gioce90]

Hi @BlueBasher , thank you for your answer.
Okay, I think I will proceed in the same way.
I tried publishing on my DevOps organization and do "remote debugging", but is really tricky. I do successful with the "hub" example of MS, but I can't do the same for tasks. Patience.

[BlueBasher]

Yes indeed, for my other extension (which is UI extension) I'm able to debug remotely as well.
For task extension I've never found a way to do it, so I've stuck with pushing my local version directly to a sandbox org.

And by the way, thank you for helping out! Think this would be an amazing addition to the extension!

[gioce90]

Hey folks, I'm going to take a stab at this unless someone is already working on it. I have an internal ado org I'll be testing with before I send a PR

Of course, I'd be really grateful for that too!

[gioce90]

Hi @chrisevett have you some news about this? :)