fix: estimate order not maintained in create/ update modal.#3326
Merged
sriramveeraghanta merged 2 commits intodevelopfrom Jan 8, 2024
Merged
fix: estimate order not maintained in create/ update modal.#3326sriramveeraghanta merged 2 commits intodevelopfrom
sriramveeraghanta merged 2 commits intodevelopfrom
Conversation
aaryan610
approved these changes
Jan 8, 2024
sriramveeraghanta
pushed a commit
that referenced
this pull request
Jan 22, 2024
* fix: estimate order not maintained in create/ update modal. * fix: estimate points mutation on update.
sriramveeraghanta
pushed a commit
that referenced
this pull request
Jan 22, 2024
* fix: estimate order not maintained in create/ update modal. * fix: estimate points mutation on update.
This was referenced Mar 15, 2024
vamsikrishnamathala
pushed a commit
that referenced
this pull request
Aug 7, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Following the update to version v0.14-dev, there's a bug affecting the order of estimates. Users have reported that despite setting estimates in a specific order, the system automatically reorders them alphabetically upon saving. This behavior is a deviation from previous versions where the user-defined order was maintained.
Steps to Reproduce:
Solution
The issue was due to unsorted data in the create/ update modal. The backend sends estimate points in
{key, value}pairs, with keys indicating order. To resolve it, I sorted these pairs by key value for proper ordering.Reference
estimate.ordering.1.mp4
Other Issues Fixed: