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.
Any background context you want to provide?
When requesting filtered properties with the
/api/v3/properties/filter/
endpoint, if you leave out thecycle
param the backend defaults to the first alphabetical cycleWhat's this PR do?
How should this be manually tested?
In an org with multiple cycles, go to the Inventory List page and select any cycle that is not alphabetically sorted first
Select a few records, and then open the Merge modal
Ensure that the data appears as expected
Go to the Inventory Map page
Toggle between different cycles, ensure that different (and correct) data appears for each cycle