"Consolidate build images" workitem should not be shown on Build Analysis
See original GitHub issueA negative sentiment was registered against feature: DeveloperWorkflowGitHubCheckTab
The “Consolidate build images” workitem is not affecting the PRs in any way. It should not be shown in the Build Analysis results:
Ongoing critical infrastructure issues
❌ Consolidate build images
Feedback submitted by @jkotas, who requested further communication regarding this issue.
Parameters
c = e468f04ae79f ut = 0 s = 2022-09-29T12-35-28 ub = 1 ki = 0 rb = 0 rt = 0 e = 0 r = dotnet/runtime __cm = 1 __fi = c8612f5632ac4af9a640a29b76d4f7a7
Issue Analytics
- State:
- Created a year ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Why azure-api does not show build related work items?
1 Answer 1 ... What connections are made between the build and the workitem when we run the build? How we can get...
Read more >Workitem title not displaying properly
Hi Everyone,. I am facing one issue in which the workitem title is not displayed properly in business users inbox.
Read more >How to retrieve all work items associated with a release ...
Click the Repositories and the Branches Menu in the Azure DevOps Portal . · Locate in the branch list the one you are...
Read more >Pull request incorrect behavior with determining, tracking ...
Clearly based on issues above newly added work item is not appearing under build summary as it is not associated with any commit...
Read more >Work items and work item types
In this case, a work item scheme would be defined as a set of types with certain characteristics (some widgets enabled, others not),...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Right. There is missing clarify about what “Critical” label means. The label is not self-describing, and it has no long description either. People are likely to going to use to mark anything that they feel is important: Epics, Workitems, … .
I’ve removed this from the Ongoing Critical Infrastructure issues for now. There’s an ongoing discussion in https://github.com/dotnet/arcade/issues/10882 for us to figure out a better strategy of using this feature than for announcements. Closing this issue.