Page History

...

1. Go to the Home page
2. Fill the form "Check branch/PR":
   
   1. Leave base branch empty.
   2. Enter branch from TeamCity ("pull/<pull-request-number>/head").
   3. Press "Latest" button to compare with the latest master.
3. On the appeared page you can see a table with failed tests and suites. Also, you can see test's failure rate for last 100 runs of master branch.
   Most important failures are placed under "Possible Blockers" header in the table. You must fix need to fix them or ensure that they aren't yours before moving ticket to Patch Available.

...

1. Go to the Home page
2. Fill the form "Check build" with build ID from TeamCity.
3. On the appeared page you can see a table with failed tests and suites. Also, you can see test's failure rate for last 100 runs of master branch.Most important failures are placed under "Possible Blockers" header in the table. You must fix them or ensure that they aren't yours before moving ticket to Patch Available.

Print possible blockers to the JIRA ticket:

1. Go to the PR/Branch check page
2. Fill the form "Notify JIRA":
   1. Enter branch from TeamCity (or "<pull-request-number>" only).
   2. Enter JIRA ticket number. If PR is named according to contributing guide (name starts with "IGNITE-"), you can leave this field empty.

Trigger "Run All" and comment JIRA by one button:

...

Lets name result 2 as critical failure. So it is required to have 5 non critical failures and 4 critical to generate notification: ....(0/1)(0/1)(0/1)(0/1)(0/1) 222....

You need to fix