How to preserve an Azure DevOps work-item discussion
A work-item comment export helps retain the context behind a requirement, bug or implementation choice. The work-item identity and message sequence make the result useful to another reviewer.
Start with the right material.
- What you provide
- one opened Azure DevOps work item with the comments you need expanded.
- The intended result
- Readable discussion from one work item.
How the workflow works.
Capture the readable discussion with available author and time details. Keep links and quoted technical material with the relevant message, separating them from unrelated interface activity.
What to check in the result.
Check the selection and order before sharing. The export covers supplied work-item content and should not be described as a complete project history or a review of linked resources.
Import the CSV with a consistent delimiter and inspect text identifiers, dates and amounts before using spreadsheet totals. Keep the original file available while checking any automatic type conversion.
Learn from the worked example.
The downloadable CSV example uses these columns: Item, Author, Displayed date, Comment, Source URL. Compare a complete record with the source before sorting, combining or importing your own output.
The supplied example is illustrative. It is not a recorded run on your data.
Download the example ↓Use it with your own material.
- Open the source you want to work with and activate WebAct on that tab.
- Copy the task from the hero, add any required fields or preferences, and review the proposed actions.
- Compare the first result with your source. Ask for a specific correction or refinement where needed.