Issue with YouTrack integration in muted tests

Avatar
Cyril Coqueugniot
Created

Hi,

When we mute tests with a comment linking to our integrated YouTrack, we're accustomed to being able to see a link to the YouTrack issue next to the muted test. Instead, we just get some HTML that we can't click on. The YouTrack integration seems to be working when we go to the project settings and test it, however.

Here's the text we get when we mouse over where the link should be:

<script type='text/javascript'>BS._IssueDetails_ETNG_35018__Root = new BS.IssueDetails('_ETNG_35018__Root_content', 'ETNG-35018', 'PROJECT_EXT_4', '_Root');</script><span class='pc' style='padding-right: 0;'    onmouseover='BS._IssueDetails_ETNG_35018__Root.stopHidingPopup();'    onmouseout='BS._IssueDetails_ETNG_35018__Root.hidePopup(300);'><span class='pc__label'><a href='https://youtrack.ourdomain.com/issue/ETNG-35018'>ETNG-35018</a></span><span class='pc__toggle-wrapper'>&nbsp;<span class='icon icon16 toggle' id='_ETNG_35018__Root'     onmouseover=

And here's what we're seeing:

Votes

0

Share

2 comments
Avatar
Denis Lapuente
Created

Hi Cyril,

this looks just like a UI issue. As we don't "call home" for features (only for version checking, and statistics sharing if enabled in the options), if this started to fail recently without any update on the server on your side, I would recommend checking your browser. Maybe some update, some wrong cache, or some plugin (if it impacts multiple users) changed something.

If this started to happen after an upgrade or similar, it would be useful to understand what changed on TeamCity or YouTrack, so that we know what happens.

0
Avatar
Cyril Coqueugniot
Created

Hello Denis!

Thanks for responding. For what it's worth, this occurs for everyone in our company, on every browser. We believe that the issue first started occurring when we upgraded to TeamCity 2017.2.3, but the users did not bring it to our attention immediately. YouTrack has not been updated in some time, and there have been no other meaningful changes on either server, aside from OS updates.

I also opened a ticket about this, and Yegor Yarko responded saying:

This problem has recently been identified and the fix should be available in the 2017.2.4 release which we plan within weeks.

Are there any additional steps we can take to resolve this, or should we just wait for the new version of TeamCity?

0

Please sign in to leave a comment.