Track JIRA + Agile with Yoke

Yoke.io uses Atlassian JIRA APIs to report on key metrics such as the number of issues in one of your favorite reports.

About the integration

Yoke uses basic authentication and secure REST APIs to connect to Atlassian JIRA and JIRA Agile products. Note that we are unable to use JIRA's OAuth because Yoke can not be defined as a linked application across all JIRA instances at this time.

If you use Google authentication, please visit your Profiles and update the password first. You can then use the user name and password in Yoke.

Card Types for JIRA

You can track the following measures in your JIRA account:

  • open issues assigned to me
  • open issues reported by me
  • issues in one of my "favorite reports"
  • issues matching a JQL search

Additional card types for JIRA Agile

You can track the following measures from a JIRA Agile Board:

  • stories in an upcoming sprint
  • incomplete stories in the current sprint assigned to anyone or just myself
  • incomplete tasks & bugs in the current sprint assigned to anyone or just myself

Slack integration

You can query your JIRA and JIRA Agile cards from Slack using slash commands.

Automatic bookmarks in Chrome

The Yoke Auto-Bookmarks Extension turns the issues, stories, tasks and bugs picked up by your JIRA cards into bookmarks in Chrome.

Tips for Yoke users

JIRA is an extremely powerful feature-rich tracker with comprehensive reporting and search capabilities.

Reports in JIRA created using the user interface or JQL, can be saved as favorite reports and tracked as Yoke cards

  • Managers can use Yoke cards based on their favorite reports to stay up-to-date on important activities.
  • Software developers and testers can track open issues assigned or reported (resp).
  • Support engineers can track the issues they created based on a customer ticket system like Zendesk.

The correct use of JIRA fields is critical to getting the right reports for different people in the team. Here are some tips on the usage of fields:

  • All projects must have a well-defined spec for the "Type", "Status" and "Resolution" fields. These will be different for regular, maintenance and agile projects.
  • Large projects can use "Priority" for escalation, "Labels" and "Components" for delegation to specialized teams, and "Fix Versions" for scheduling.
  • Agile projects must use sprints, not "Fix Versions".

JIRA Agile is built on top of JIRA; so you can leverage the standard cards based on open issues, JQL and favorite reports. Here are some tips:

  • Scrum masters should track the incomplete stories in the current sprint.
  • Product owners/managers should track the stories in an upcoming sprint to make sure that the specifications are ready.
  • Other agile team members can track incomplete tasks & bugs in the current sprint assigned to them.

The Yoke Auto-Bookmarks Extension helps you quickly access critical issues and stories related to the current iteration.

cardclone front