"Fixed in Build" updating one build late

using TeamCity 8.0.3 (build 27540) and  YouTrack 5.0.3

I am finding that 'fixed in build' is updating but it is not set until after the next build occurs. A typical workflow would be:

1.   push to central mercurial repo with '#Foo123 Fixed'
2.   TeamCity automatically performs build, eg Build-001
3.   Go to youtrack and 'Get changes from TeamCity now'
4.   Issue changes from previous state to 'Fixed' (Fixed in build remains 'Next Build')

I expect 'Fixed in Build' to get updated to 'Build-001' in Step 4. Its not until I do the next commit that the 'Fixed in Build' for #Foo123 will get updated, however it will have 'Fixed in Build'=Build-002 !

I dont understand why in step 4) the 'Fixed in build' tag isnt updated with the value 'Build-001' as it 'knows' the issue is fixed from TeamCity as it was able to change it from InProgress->Fixed.

What am i missing?
5 comments
Comment actions Permalink
Hello Wallace,

Thank you for your question.
That is how it works:


The field gets updated by the integration provided one of the conditions applies:
1. the issue is resolved by the moment the integration notices the build, but after the previous build (in other words, it's resolution date and time is bigger then those of the previous build) and 'Process Resolved Issues' option is enabled in TeamCity Mapping/Actions dialog
2. the issue is resolved by the moment the integration notices the build and it's mentioned in the build

Thank you.
0
Comment actions Permalink
Andrey, thanks for your response.
Do you think its a bit strange/could-be-better that it can set a better (closer) 'Fixed in Build' value for a given youtrack issue ?
0
Comment actions Permalink
Wallace,

The problem solves if you follow the second condition.
Could it be the solution for you?

Thank you.
0
Comment actions Permalink
The problem solves if you follow the second condition.

Yes, how do you do that ?
0
Comment actions Permalink
Whenever an issue is closed after the last known successful build but before a new successful build, TeamCity integration fills the issue's 'Fixed in Build' field with the number of the new successful build once it has been assembled.


What appears to be happening (please clarify) is Youtrack detects the issue is fixed (closed) AND the successful build at the same time so it must not realise its fixed in that build and thus doesnt update the 'fixed in build' until the next build which I think is wrong
0

Please sign in to leave a comment.