search

ipatalas / vscode-sprint-planner

Plan your sprints in VSCode directly!
MIT License
36 stars 21 forks source link

Feature Request: Hide Completed Items #31

Open sheldonhull opened 3 years ago

sheldonhull commented 3 years ago

I'm evaluating a PBI that has been carried over from a prior sprint. This means the completed items from that show up, but due to the Estimated Effort being locked, it will recreate the work-item as a duplicate. This makes it hard to seperate out my new planning from prior work.

Can we consider an option to "hide completed" items in the synced items from Azure DevOps to avoid this conflict?

ipatalas commented 3 years ago

Oh... that's a big overlooking. Absolutely good point. We were doing exactly the same in the days I was using Azure DevOps. I'll have a look into that somewhere soon.

Tom4U commented 1 year ago

Much better from my point of view would be marking completed tasks with strike-through formatting (if possible) and even move them at the end of tasks. Maybe support for collapsing would be an idea, too.

sheldonhull commented 1 year ago

Not using any more so feel free to close if needed. Cheers

Tom4U commented 1 year ago

I definitely still like to see that feature :)

ipatalas commented 1 year ago

The original idea of the extension was to just initially plan the sprint, not to manage it. The reasoning was simple: adding many User Stories with a bunch of tasks at once was cumbersome and frustrating. Therefore it never contained any features for closed tasks nor anything like that was ever planned. It was supposed to solve our problems back in the days and it did :) I published this mainly for our teams back then but since this is a very generic problem I was happy others found it useful too. Unfortunately last time I worked with Azure DevOps was couple of years ago so I naturally lost interest in developing it. Also my life priorities have shifted in last 2-3 years as the world has changed since then. I was doing that in my spare time only so that basically means I cannot promise any changes in near future but I'm open to small bugfixes, PRs or a new maintainer. This may and probably will change as soon as I change the company I work for and I will get back to Azure DevOps struggle again. However it's kinda the best place I've been in so far so you know... ;)