microsoft
Extension should not change the WSJF value for empty input fields
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
Hello folks - thanks for raising this topic. Right now our ADO Project is facing the same issue. When the WSJF fields are empty, the field that shows the rating (Called in this Extension as 'WSJF') sets automatically the value to = 0. Which obligates the User to whether Discard changes or Save the card. This is aggregating an unnecessary step to the process. Has this been resolved already or can you suggest how we can fix it by ourselves without uninstalling the Extension? Thank you.
We are having this same issue, and it is preventing us from using the extension at all. We need to pilot its use in a few groups before we determine if we're going to do a larger, enterprise wide rollout. Considering the other 'input' fields that calculate WSJF are blank (null), it seems counterintuitive that WSJF would calculate as zero and, therefore, force users to save a change they didn't make.
This becomes even more problematic for us because, through our pilot, we are keeping the input fields + WSJF field hidden on Features so other users don't see them. The pilot groups are using field columns in queries and backlogs to input the data as a workaround. However, this is no longer a feasible pilot option because ALL users are being asked to save Features so the WSJF value saves down.
Please fix this or we won't be able to use the extension at all.
Similarly, I would expect that when all input field values are populated (and saved down), the WJSF value would auto-populate based on the backend calculation and would not require another manual save action on the card.
For example, in the pilot I mentioned above where we are populating the input values through column edits in backlog and query views - in this scenario, all input values exist and have been saved to the record. However, the WSJF value does not appear and is not populated unless we manually open the card and save it back down.
In my mind, WJSF should reflect the output of the 4 other input fields; it should not require any manual steps to update or save it down to the card. Instead, the manual steps would be focused on populating and saving the inputs.
Please advise as we would really love to use this extension, but are currently at a standstill until this is fixed / updated.
Hello, just checking in, any updates on this issue and what the path might look like to resolve it? Our organization is heavily vested in tracking WSJF on Features in ADO, but this is a blocking issue for us currently. Happy to chat if that would be helpful.