How to get TeamCity mapping to work?

Can someone please provide me with screenshots or written out configuration for a TC mapping that works for them in YouTrack ?

Preferably one that does the following:
1. add build number to Builds bundle.
2. set "Fixed in build" = build number from TC.
3. change state field to something/anything.
4. attaches vcs comment to issue in TC tab.

I have an issue open but aren't having much luck in getting any help and unfortunately I'm running out of time before my managers decide against youTrack if I can't get it to do what I told them it would:

http://youtrack.jetbrains.com/issue/JT-18309


For some odd reason, this worked ONE time in my many attempts in many different clean installs of YouTrack.
7 comments
Comment actions Permalink
I think I am just realizing that what i'm trying to do is not supported in YouTrack 4.2 or earlier...

I need TeamCity successful build to trigger on all issues mentioned in vcs comment:
1. set State = "Pending QA" (unresolved)
2. set fixed in build = TC build #....

So my vcs comment might be:
fixed some issues..
  1. MyProject-1
  2. MyProject-2
  3. MyProject-3


and I'd expect issues 1,2,3 to be set to "Pending QA" and fixed in build be set to the TeamCIty build #..

It's not supported, right?

My backup plan is to add a step in my TC project configuration that does this via YouTrack REST API.. any foreseeable problems with that approach?
0
Comment actions Permalink
Hi Diego,
This scenario is supported. I'm now looking at the database you've provided and will get back to you today.

Alexander
0
Comment actions Permalink
Hi, thank you for looking into this! The documentation reads "Whenever an issue HAS BEEN CLOSED AFTER last known successful build but before a new successful build, TeamCity integration fills the issue's 'fixed in build' attribute with the exact number of the new successful build once it has been assembled"

The problem is i want TeamCity to be the one to move the issue along the workflow in YouTrack. So ideally, a developer can just do a checkin into main branch and not go back to YouTrack to update state. The problem is that my target state "Pending QA" is not a closed/resolved state.. I'd like a build number for anything that goes to QA so it can't be a resolved state.
0
Comment actions Permalink
Diego, I was not completely correct stating that your scenario is supported. The thing is YT-TC integration will only apply actions specified in a mapping to Resolved issues. Please have a look at JT-10056 for some discussion on how this should be improved and feel free to share your thoughts.
As a workaround, I can only suggest that your developers first transfer an issue to some resolved state (either manually, or via VCS comment command).

Alexander
0
Comment actions Permalink
Ok, thanks! If i leave the TC mapping configured will it still add the build numbers to the bundle even if no resolved issues are found during the sync ?
0
Comment actions Permalink
Only if you select 'Add each build' option.
0

Please sign in to leave a comment.