snuziale / vsts-extension-split-work Goto Github PK

We need to keep backlog order of newly created continuation work resulting from item splitting to be just after the original predecesor.

Thank You
Marek

No split occurs when subject field contains nordic letters ...

We can't seem to get the Split to work on Bug work item types. Nothing ever happens. Is this a bug?

need to know what the license is for this so my procurement office can authorize it's use

After splitting an item, you'll see a message similar to "This work item was split from work item 12345." When you click the link for "12345" you get an HTTP 404 message.

Hi
I am using TFS 2015.2 on-premises.
I was download the Split and upload to my team project. but it is not work! as you can see in Fig.

the Split option does not added to menu!

Hello,

Is there a known issue with AzurDevOps currently concerning splitting work items?
It seems like, since last week, whenever I split work items such as stories, the splitted item itself and the child items end up everywhere except for the correct iteration (which should the current iteration + 1).

This issue occurs intermittently, some stories that I split behave as expected, but sometimes not.

Hi there,

Would it be possible to support a "reverse" split (e.g. move the tasks that are done to a new PBI and keep the original PBI with the work that is not done yet)?

The reason behind it: related work done outside of Azure DevOps (like linking commits to the story etc) could then keep using the original ID.

There was also a somewhat related request under Q&A below about the commits - in my interpretation of the split, all commits would be either linked to both PBIs or would stay with the original one (which will be used to continue work).

PS if this one is supported, i suspect #8 will automatically be addressed as original PBI also keeps its backlog order.

I cloned the repo, ran npm install, then grunt build, and I get the following:

C:\Users\Paul.Abrams\Source\Repos\split-extension>grunt build
Running "ts:build" (ts) task
Compiling...
Using tsc v1.8.9
node_modules/vss-web-extension-sdk/typings/vss.d.ts(21866,29): error TS1005: '='
expected.
node_modules/vss-web-extension-sdk/typings/vss.d.ts(21874,21): error TS1005: '='
expected.
node_modules/vss-web-extension-sdk/typings/vss.d.ts(21874,30): error TS1005: ';'
expected.
node_modules/vss-web-extension-sdk/typings/vss.d.ts(21875,21): error TS1005: '='
expected.
node_modules/vss-web-extension-sdk/typings/vss.d.ts(21875,41): error TS1005: ';'
expected.
node_modules/vss-web-extension-sdk/typings/vss.d.ts(21876,29): error TS1005: '='
expected.
node_modules/vss-web-extension-sdk/typings/vss.d.ts(29398,21): error TS1005: '='
expected.
node_modules/vss-web-extension-sdk/typings/vss.d.ts(29398,45): error TS1005: ';'
expected.

8 syntax errors
Error: tsc return code: 2
Warning: Task "ts:build" failed. Use --force to continue.

Aborted due to warnings.

Split is failing with 400

{"$id":"1","customProperties":{"FieldReferenceName":null,"FieldStatusFlags":"none","ErrorMessage":"TF401320: Rule Error for field Injected. Error code: Required, InvalidEmpty. One additional error occurred during validation of the work item. Please correct all errors and try again.","FieldStatusCode":0,"RuleValidationErrors":[{"fieldReferenceName":"ABLScrum.Injected","fieldStatusFlags":"required, invalidEmpty","errorMessage":"TF401320: Rule Error for field Injected. Error code: Required, InvalidEmpty.","fieldStatusCode":524289,"ruleValidationErrors":null},{"fieldReferenceName":"ABLScrum.SecurityIssue","fieldStatusFlags":"required, invalidEmpty","errorMessage":"TF401320: Rule Error for field SecurityIssue. Error code: Required, InvalidEmpty.","fieldStatusCode":524289,"ruleValidationErrors":null}]},"innerException":null,"message":"TF401320: Rule Error for field Injected. Error code: Required, InvalidEmpty. One additional error occurred during validation of the work item. Please correct all errors and try again.","typeName":"Microsoft.TeamFoundation.WorkItemTracking.Server.RuleValidationException, Microsoft.TeamFoundation.WorkItemTracking.Server","typeKey":"RuleValidationException","errorCode":0,"eventId":3200}

The fields are a custom field that is a boolean.

We need to copy state to newly created continuation work resulting from item splitting.

Thank You
Marek

Trying to split a deliverable like I have done in the past. It fails (new Edge and Chrome).

Here's the console output:
Content?bundle=vss-bundle-basejs-vwCtrJpcLWiIeuyIlqmSJGfIBPaSLZgklw3ecEhDqrpw=:5 POST https://microsoft.visualstudio.com/OS/_apis/wit/workItems/$Deliverable 400
send @ Content?bundle=vss-bundle-basejs-vwCtrJpcLWiIeuyIlqmSJGfIBPaSLZgklw3ecEhDqrpw=:5
ajax @ Content?bundle=vss-bundle-basejs-vwCtrJpcLWiIeuyIlqmSJGfIBPaSLZgklw3ecEhDqrpw=:5
(anonymous) @ Content?bundle=vss-bundle-ext-core-vY_2nznYWOwJihxedCsWuVCTPaGS_j6G4HtzFf9lE4jQ=:265
c @ Content?bundle=vss-bundle-ext-core-vY_2nznYWOwJihxedCsWuVCTPaGS_j6G4HtzFf9lE4jQ=:233
(anonymous) @ Content?bundle=vss-bundle-ext-core-vY_2nznYWOwJihxedCsWuVCTPaGS_j6G4HtzFf9lE4jQ=:233
u.promiseDispatch @ Content?bundle=vss-bundle-ext-core-vY_2nznYWOwJihxedCsWuVCTPaGS_j6G4HtzFf9lE4jQ=:233
(anonymous) @ Content?bundle=vss-bundle-ext-core-vY_2nznYWOwJihxedCsWuVCTPaGS_j6G4HtzFf9lE4jQ=:233
t @ Content?bundle=vss-bundle-ext-core-vY_2nznYWOwJihxedCsWuVCTPaGS_j6G4HtzFf9lE4jQ=:233
Content?bundle=vss-bundle-ext-core-vY_2nznYWOwJihxedCsWuVCTPaGS_j6G4HtzFf9lE4jQ=:265 Uncaught (in promise) TFS.WebApi.Exception: TF401319: Rule evaluation failed for field Release.
at g (https://microsoft.visualstudio.com/_public/_Bundling/Content?bundle=vss-bundle-ext-core-vY_2nznYWOwJihxedCsWuVCTPaGS_j6G4HtzFf9lE4jQ=:265:499)
at https://microsoft.visualstudio.com/_public/_Bundling/Content?bundle=vss-bundle-ext-core-vY_2nznYWOwJihxedCsWuVCTPaGS_j6G4HtzFf9lE4jQ=:265:3594
at nt (https://microsoft.visualstudio.com/_public/_Bundling/Content?bundle=vss-bundle-ext-core-vY_2nznYWOwJihxedCsWuVCTPaGS_j6G4HtzFf9lE4jQ=:265:763)
at https://microsoft.visualstudio.com/_public/_Bundling/Content?bundle=vss-bundle-ext-core-vY_2nznYWOwJihxedCsWuVCTPaGS_j6G4HtzFf9lE4jQ=:265:3526
at l (https://microsoft.visualstudio.com/_public/_Bundling/Content?bundle=vss-bundle-ext-core-vY_2nznYWOwJihxedCsWuVCTPaGS_j6G4HtzFf9lE4jQ=:233:8126)
at https://microsoft.visualstudio.com/_public/_Bundling/Content?bundle=vss-bundle-ext-core-vY_2nznYWOwJihxedCsWuVCTPaGS_j6G4HtzFf9lE4jQ=:233:8352
at t.when (https://microsoft.visualstudio.com/_public/_Bundling/Content?bundle=vss-bundle-ext-core-vY_2nznYWOwJihxedCsWuVCTPaGS_j6G4HtzFf9lE4jQ=:233:3784)
at t.u.promiseDispatch (https://microsoft.visualstudio.com/_public/_Bundling/Content?bundle=vss-bundle-ext-core-vY_2nznYWOwJihxedCsWuVCTPaGS_j6G4HtzFf9lE4jQ=:233:2828)
at https://microsoft.visualstudio.com/_public/_Bundling/Content?bundle=vss-bundle-ext-core-vY_2nznYWOwJihxedCsWuVCTPaGS_j6G4HtzFf9lE4jQ=:233:1653
at MessagePort.t (https://microsoft.visualstudio.com/_public/_Bundling/Content?bundle=vss-bundle-ext-core-vY_2nznYWOwJihxedCsWuVCTPaGS_j6G4HtzFf9lE4jQ=:233:5777)

When splitting an item, it would be nice to autoname titles by adding a number sufixes etc.:
Example:

• My Work
  split into
• My Work - 1
• My Work - 2
  then
• My Work - 2
  split into
• My Work - 2
• My Work - 3
  etc.

Trying to use the Split function is not working on User Story. Tested this on a different collection and it works. The failing collection does have modifications to the User Story WIT. Custom fields, additional tab, hidden fields.
The console output doesn't show anything after clicking the Split button in the dialog.
Running v0.1.6 of the Split extension.
TFS 2018.2 OnPrem

I suspect this is happening because of one of our custom fields but don't know which one or how to identify it, or if there is a way to fix it.

Hello,
This extension uses hard coded names of "closed" states. It is hard coded in scripts/dialog.tsx line 12:
var ExcludedWorkItemStates = ["Closed", "Removed", "Cut", "Done", "Completed"];

But in real world these names can be customized in TFS process template and then identified as "closed" in ProcessConfiguration.xml file.

Please get the names of closed states from that place to make it working with customized configurations.

We need to add predecessor and successor links between the split items.

Thank You
Marek

Since upgrade to 0.1.7 we're not seeing Split option on our work items. Our Azure DevOp Servers are 2021 Update 1 RC2 (18.181.31202.2 (Dev18.M181.5).
In the browser console we're getting error:
Error: Timed-out waiting for menu source provider for contribution: blueprint.vsts-extension-split-work.vsts-extension-split-work-action at Content?bundle=vss-bundle-common-vI-kzMYIKWmtwxb4U_euZon-W7872GSMRlrOgh4eNqEk=:33:12238

Split functionality was working till 19-Feb, but it stopped working now on Azure DevOps Services.

Steps to replicate:

1. Go to Feature
2. Click on Split option
3. Select the open work item option
4. Click on Split
   Expected result: New Feature should be created and all active stories should move under the new Feature

Actual Result: Nothing happening, Feature was not created, No success or error message shown THIS IS HIGH PRI FEATURE FOR OUR Enterprise orgs, since we are having PI planning soon and we would like to split multiple items before the PI meetings.

I ran this on a bug that had a development task in the prior sprint, expecting that it would create a new task and transfer the remaining time and other details (but not completed time), assign that new task to the current sprint, and then close the prior task.

Instead it just set the current task to the base iteration. Why is it doing this, or how can I troubleshoot it?

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

If you try to remove one of the linked work items from the list the following error appears in IE11 Version 11.483.15063.0

Line: 14
Error: Object doesn't support property or method 'assign'

No change. Split is still not working for User Stories.

UPDATE: see additional comment below for more defect details.

When attempting to split a Feature work item type, the "Split" button has no effect. The button appears to clean (css color changes occur) but the popup does not change or disappear and no error message is show... nothing happens. Repeated clicking on the button also has no effect. Changing the Title, selected PBI childres, and the checkbox and clicking the split button also has no effect. Clicking the Cancel button does cause the popup to disappear.

It appears that Split only works on PBIs and Bugs.

Hi,

We currently use this Split function in Azure DevOps and we love it. Saves so much time and effort.

There is just one thing we would change, if we had the chance; Is there any way we could include all the information that was on the previous User Story? For us, the biggest thing would be to copy over the discussion.

I guess the ultimate would be to make the plugin configurable, so we decide what gets copied and what doesn't. But i'm sure that would be a far bigger task.

Thanks, Andrew.

The Split functionality doesn't work in Chrome browser.

P S It works with Internet explorer

Looking forward for the fix of this issue at the earliest

I installed the extension in our VSTS account. When opening the menu of a work item the menu item appears, but the text is missing:

Also clicking on the item doesn't start any operation (also no error logged in console)

It is unclear when using the Split tool what iteration incomplete work will be moved to, and after using the tool (TFS 2015 update 3 on prem) we have experienced the work being moved to random/inconsistent past iterations.

Eg: with these 4 example iterations:
Past

• 2017-06-23 Release
• 2017-07-07 Form Rework
  Current
• 2017-07-21 SIM Release
  Future
• 2017-08-04

"Splitting" PBIs from the 2017-07-21 release we would expect them to goto the 2017-08-04 but some went to 2017-06-23 some went to 2017-07-07.

We need to split Effort by a percentage done to support proper sprint velocity tracking and plan forecasting.
Thank You
Marek