Integrate YouTrack With GitHub!

Great news for all GitHub and YouTrack users. Today, we are introducing native integration between YouTrack and GitHub.
What will you get? You can type any command (just as with command window) right in the commit comment, and this command will be applied to the issue associated with commit. For example, should you commit files with a comment like #JT-1787 fixed tag to be documented, issue JT-1787 will be fixed and tagged as “to be documented”.
Interested? In order to integrate your YouTrack installation or hosted instance with GitHub repository, you’ll need to navigate to Admin->Service Hooks part of your repository and find YouTrack at the bottom of the list of available service hooks. You’ll also find all necessary instructions in service hook description.
Note: if you’re using YouTrack 2.x version, the command specified in commit comment will be applied with the administrator credentials, if you’re using YouTrack hosted, and generally starting from the next YouTrack version, the command will be applied with the committer’s credentials.

Integrate and track with pleasure!
JetBrains YouTrack Team

This entry was posted in features, tips and tagged , . Bookmark the permalink.

9 Responses to Integrate YouTrack With GitHub!

  1. Chris Jackson says:

    Any advice on how to troubleshoot this?

    Pushing a commit to GitHub with the message “#admin-16 fixed” doesn’t seem to do anything. My email address is the same in YouTrack and GitHub’s user settings. Also, in the YouTrack service hook on GitHub, if I click “Test Hook” I get the message “Payload deployed”.

  2. Jovo says:

    Hi,

    we defined a custom state for our issues. Is there a way to set this state through a GitHub commit message via service hooks?

    greetZ,

    Jovo

    Note: The state contains whitespace characters.

  3. Steve Sheldon says:

    Hey Guys, I have a workflow question…

    Let’s say in Github I work on a feature branch called “Feature” and we had a main branch called “V 1.0″. Our build for the test team will be built from the “V 1.0″ branch. Now let’s say I do a commit and push for a bug fix into the “Feature” branch.

    It will now go up on github for code review but it isn’t in the branch used for test builds yet, so if the bug is marked fixed it’s premature.

    Once the code review has passed, the change will be merged into the “V 1.0″ branch. At this point we want the you track bug to be marked as fixed.

    What I am getting at is if there is a way to have put the commands for youtrack in the commit on the feature branch and specify a way to say, only run them when committed to the “V1.0″ branch. I am looking to have a way to have some accountability for each bug and control the timing of the updates without losing all the benefits of Git.

    Thanks, Steve

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code class="" title="" data-url=""> <del datetime=""> <em> <i> <q cite=""> <strike> <strong> <pre class="" title="" data-url=""> <span class="" title="" data-url="">