cschleiden / azure-boards-decompose

Azure Boards extension to quickly decompose work items into a valid hierarchy

cschleiden

I currently work at GitHub. Before that I worked at Microsoft in Redmond on Azure Boards and before that as application development consultant for Microsoft Germany.

Find me @cschleiden, https://cschleiden.dev/, and https://www.linkedin.com/in/cschleiden/.

Most active projects

• go-workflows - durable workflow-as-code engine in Go https://github.com/cschleiden/go-workflows

Blog

• Effective Workflow GitHub CLI extension
• go-workflows: Durable Workflows in Go Part 2
• Simple task queue with Redis Streams
• go-workflows: Experiments with Go Generics
• go-workflows: Durable Workflows in Go Part 1

azure-boards-decompose's Issues

blank page

Hi,

I install it and when I open it, I have a blank page.

Any idea ?

Thanks

Error on backlog iteration when using Decompose

Hi,

If I try to use the extension in the backlog or the board, it works fine. If I try in Queries or Plans, it raises the following error :
TF400497: The backlog iteration path that you specified is no longer valid.

Is it supposed to work in these sections? Thanks!

On premises

Do you have plans to make it work with on premises TFS? are there any reasons why it cannot work?

Dialog needs a scrollbar

Feature Request: Being able to copy and paste a list and new lines = new items

A lot of the time when we are decomposing items we might take a bunch of requirements that are in the story which are already bullet pointed out.

It would be nice if we could cut and paste multiple lines and have them decompose into multi items.

ie: Copy this:
I want ui to do this
I want ui to do that
Backend needs this

Creates 3 decomposed items that we can allocate levels as needed.

test

Decompose doesn't open when triggered from work item form

Cannot decompose Epics when Feature level is disabled

The extension should honor the settings of work items - if Feature level is disabled, I should be able to create Product Backlog Items directly under Epics.

Work Item Mandatory Field

When a WorkItem has a mandatory field, the extension does not save the changes, and all your work is lost.
Ex: Team is a mandatory field for us. I am on multiple teams. Is there a way for the decompose to either show mandatory fields and let us set them or provide a popup that lets us set them before or after so our work is not lost.

Error given: TF401319: Rule evaluation failed for field Team.

Setup CI/CD with Azure Pipeline

Decompose Work Item not bringing up the usual pop-up option to add Work Items

It was working fine earlier today. Now it does not seem to be bring the usual pop-up window to add the Work Items

no license file

please add a license agreement file

Error "Incompatible API version (3.0)"

I am trying to install the extension in TFS 2015.3 and I am getting the error "Incompatible API version (3.0)"
Maybe I downloaded the extension for TFS 2017?
where can I download the extension for TFS 2015.3?

Thanks

Extension is unpublished from marketplace

Could you republish it back? Critical thing 🙂

Decompose no longer works in Azure Devops

Been working for a while. Now all of a sudden if I click on Decompose and enter a few tasks in a PBI the "Create" button is still enabled but clicking on it doesn't produce any results.

Happens to all users in my org.

Upgrade to latest version of SDK

Register menu item as action instead of action-provider

To improve performance of loading please register the menu item as an action instead of action-provider.

Support creating Tasks inside Tasks (because it is allowed)

It is possible that a Task can have other Tasks as childs.
So it should be possible from within Decompose to do exactly that :-)

Thanks for this great component!!

Decompose returns a blank form

When right-clicking on Decompose Work Item, it only returns a blank window with none of the expected functionality. Any changes or issues to be aware of that might have caused this?

Saving items does not work with Internet Explorer

Error because Object.assign is not available and used by spinkit

click "decompose work items" but nothing happens

installed on our visualstudio.com instance, but it doesnt seem to work.

Publishing from command line results in error

Could not create package: 'Error: Command failed: tfx extension create --overrides-file ../configs/release.json --manifest-globs ./vss-extension-release.json --no-prompt --json
TypeError: Path must be a string. Received undefined
'

Might be related to node/npm 6

Support reordering work items

• Support drag and drop for mouse support, and shortcuts like "Ctrl + Cursor Up/Down".
• Move children when moving a parent

Allow setting more fields when creating work items

• One use case would be setting "Remaining Work" when creating tasks

Allow creating sibling work items

[Feature Request] Display existing children of work item being decomposed

It would be very helpful to display a list of existing work items that are part of the hierarchy. The use case is that you want to come back to a user story and continue decomposition and it has existing linked children. Having this list would alleviate any duplicate work items being created along with enabling the ability to continue work item decomposition at a later date. If you choose to implement this the existing work items should not be editable through this extension. Here is an example of how I would see the UI representing this change. Note, the work items without <> and "X" controls are those which are existing. All actions should be disabled for these.

Deactivate the comment "Created using QuickCreate"

If possible, deactivate this comment, because it will trigger unwanted events to external apps.

E.g. We connected "Teams" with VS, and each time we plan with decompose, all created workitems will pop up in Teams because the trigger is "Show on new comment".

Cannot create the bundle (vsix file)

Running npm run publish:release throwing bunch of errors, this is the npm log:

0 info it worked if it ends with ok
1 verbose cli [ 'C:\Program Files\nodejs\node.exe',
1 verbose cli 'C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js',
1 verbose cli 'run',
1 verbose cli 'publish:release' ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'prepublish:release',
4 verbose run-script 'publish:release',
4 verbose run-script 'postpublish:release' ]
5 info prepublish:release @
6 info publish:release @
7 verbose unsafe-perm in lifecycle true
8 info @ Failed to exec publish:release script
9 verbose stack Error: @ publish:release: npm run build:release && node ./scripts/publishRelease
9 verbose stack Exit status 1
9 verbose stack at EventEmitter. (C:\Program Files\nodejs\node_modules\npm\lib\utils\lifecycle.js:217:16)
9 verbose stack at emitTwo (events.js:87:13)
9 verbose stack at EventEmitter.emit (events.js:172:7)
9 verbose stack at ChildProcess. (C:\Program Files\nodejs\node_modules\npm\lib\utils\spawn.js:24:14)
9 verbose stack at emitTwo (events.js:87:13)
9 verbose stack at ChildProcess.emit (events.js:172:7)
9 verbose stack at maybeClose (internal/child_process.js:827:16)
9 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5)
10 verbose pkgid @
11 verbose cwd C:\vsts-quick-decompose
12 error Windows_NT 6.3.9600
13 error argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "run" "publish:release"
14 error node v4.4.5
15 error npm v2.15.5
16 error code ELIFECYCLE
17 error @ publish:release: npm run build:release && node ./scripts/publishRelease
17 error Exit status 1
18 error Failed at the @ publish:release script 'npm run build:release && node ./scripts/publishRelease'.
18 error This is most likely a problem with the package,
18 error not with npm itself.
18 error Tell the author that this fails on your system:
18 error npm run build:release && node ./scripts/publishRelease
18 error You can get information on how to open an issue for this project with:
18 error npm bugs
18 error Or if that isn't available, you can get their info via:
18 error
18 error npm owner ls
18 error There is likely additional logging output above.
19 verbose exit [ 1, true ]

If is possible can you compile into a bundle and share the vsix bundle too.

Thanks

Allow to cycle between multiple work item types for a backlog level

Example: "Working with Bugs" set to Requirements

Support work item type icons

Area/Iteration values lost - ruins value of the plugin

Its missing something pretty critical, but easy to add, though.
When the work items are created, they are all set at the root path for iteration path and area path.
They do not keep the context/values of the parent item you were decomposing from.
This causes the items to disappear, if you are in a team screen.
This forces the user to have to go find the items and set the values properly in order for them to return back to the team backlog. That negates a lot of the benefit.
Fix that, and I can update this to 5 stars.!