microsoft / microsoft/AzureDevOps-WSJF-Extension
Extension should not change the WSJF value for empty input fields
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 29
- Forks
- 41
- PR merge metrics
- No merged PRs in 30d
Description
The extension is problematic because it sets all work items to the "changed" status and the user has to save again.
When the extension is installed, many work items already exist and the input fields for the formula are empty for all of these work items. When a work item is viewed, the extension calculates the WSJF value and writes it to the result field, which was previously empty. This changes the work item and the user sees this status change on the additional asterisk. If the user wants to leave the page, he will be stopped and asked whether he wants to "discard changes" or "save changes".
Suggestion for improvement: the extension should not change the WSJF value for empty input fields
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the WSJF calculation performed when an Azure DevOps work item is viewed, focusing on how empty formula inputs lead to a result-field write. Done means empty inputs no longer alter the WSJF field or mark the work item as changed; the payload names no files or tests, so locate the relevant entry point and existing verification first.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100