This repository was archived by the owner on Jan 14, 2019. It is now read-only.
Changed how BuildMaster release number is matched to TFS work items for issues list#10
Open
gmarndt wants to merge 2 commits intoInedo:masterfrom
Open
Changed how BuildMaster release number is matched to TFS work items for issues list#10gmarndt wants to merge 2 commits intoInedo:masterfrom
gmarndt wants to merge 2 commits intoInedo:masterfrom
Conversation
…ems based on iteration path. Previously, the whole iteration path had to match the BuildMaster release number; now, if the release number appears anywhere in the iteration path for that work item, it will be included in the issues list for that release. Note that normal rules for filtering on area path and project still apply, so if the area path doesn't match, the work item will never be included regardless of what the iteration path is.
…aseNumber() returns the value from the customerReleaseNumberFieldName. This will anchor it properly so issues will match to the release whether a custom field or the (default) iteration path are used.
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
Previously, the whole iteration path had to match the BuildMaster release number; now, if the release number appears anywhere in the iteration path for that work item, it will be included in the issues list for that release. The normal rules for filtering on area path and project still apply, so if the area path doesn't match, the work item will never be included regardless of what the iteration path is. This is useful for people who have nested TFS iteration paths with the release at an arbitrary level in the hierarchy, e.g. Project\Area1\1.0.0\Iteration 2.