Closed jahnwa closed 3 years ago
You are on the right track: GetBacklogWorkItemTypesAndStates
use the work item types listed in PortfolioBacklogs (that is the same as Processconfiguration - Get REST API). You should add your custom type to the process backlog, in any of the categories listed in the green area of the screenshot.
This is a bit weird then. The custom work item is under "Portfolio backlogs" level, but when I use the Processconfiguration - Get REST API to take a closer look on the process, the custom work item is nowhere to be found. The response shows only "Epics" and "Features" under portfolioBacklogs.
I pushed the little app I used to test the call to https://github.com/giuliov/azuredevops-rest-api, it would be interesting to see what outputs for you.
Thanks for helping me out @giuliov , I really appreciate it.
This is the output of the app:
Epics Features Bugs Backlog items Tasks
The custom work item is not part of the output :-(
I have made adjustments to the rule that manually inserts the properties of the custom work item. However, if we ever make any changes to the custom work item with regards to the states, it is a bit of a hassle to update the rule.
Hi @giuliov, In my case with the Backlog Strategy (custom) not work auto active parent.
This is Error in Azure function: 2021-06-08T16:54:55.843 [Information] Aggregator v1.0.1 executing rule 'autoactivateparent' 2021-06-08T16:54:56.109 [Information] Connected to Azure DevOps 2021-06-08T16:54:56.114 [Information] Initial WorkItem 7635 retrieved from https://dev.azure.com/XXXXXXXX/ 2021-06-08T16:54:57.560 [Information] Loading workitem 7607 2021-06-08T16:54:58.023 [Warning] Rule 'autoactivateparent' failed: Object reference not set to an instance of an object. 2021-06-08T16:54:58.024 [Information] Executed 'Functions.autoactivateparent' (Succeeded, Id=060f1a1e-a59c-4124-acc8-7e56760f6506, Duration=2184ms) 2021-06-08T16:55:18.947 [Information] Host Status: {"id": "XXXXXXXXXaggregator","state": "Running","version": "3.0.15733.0","versionDetails": "3.0.15733 Commit hash: a0b4f7d3a2fadb61bc3e0ef99987e1701f12e310","platformVersion": "93.0.7.86","instanceId": "fd39869222317c16b91f1e567b51ce29fdb6a4cf98928b8ea11cabb1167f0465","computerName": "DW0-HR0-2543-12","processUptime": 1832061}"id": "XXXXXXXXXaggregator","state": "Running","version": "3.0.15733.0","versionDetails": "3.0.15733 Commit hash: a0b4f7d3a2fadb61bc3e0ef99987e1701f12e310","platformVersion": "93.0.7.86","instanceId": "fd39869222317c16b91f1e567b51ce29fdb6a4cf98928b8ea11cabb1167f0465","computerName": "DW0-HR0-2543-12","processUptime": 1832061} 2021-06-08T16:55:19.226 [Information] Host Status: {"id": "XXXXXXXXXaggregator","state": "Running","version": "3.0.15733.0","versionDetails": "3.0.15733 Commit hash: a0b4f7d3a2fadb61bc3e0ef99987e1701f12e310","platformVersion": "93.0.7.86","instanceId": "fd39869222317c16b91f1e567b51ce29fdb6a4cf98928b8ea11cabb1167f0465","computerName": "DW0-HR0-2543-12","processUptime": 1832339}
Does your rule uses store.GetBacklogWorkItemTypesAndStates()
? If not, please open a separate issue.
Hi, yes in fact i used the examples of https://tfsaggregator.github.io/docs/v3/rules/rule-examples-advanced/
We have a custom work item type we have created in our custom process. However, it seems the store.GetBacklogWorkItemTypesAndStates() does not include the new work item. The work item is placed at Portfolio Backlog level.
What my rule is trying to do is auto-activate all parents up to the root parent, which is the new work item (code is similar to here ). It works perfectly from "Task" to "Epic" (we have a custom Scrum process), but it does not work for the root parent. I can see that the store.GetBacklogWorkItemTypesAndStates() gets all the other work item types I require, except the root parent work item type.
Could this be because the custom work item does not have a Backlog Category (such as Microsoft.BugCategory)?
Is there a workaround for this issue?