In this article:

  • Introduction to story points
  • How do I setup Jira integration?
  • Track progress of key results in Ally.io by story points
  • Track progress of projects in Ally.io by story points
  • Common questions

Introduction to Story Points

Each organization takes on ambitious projects that are complex, and it becomes increasingly challenging for teams to meet realistic deadlines. This is where project estimation comes handy. The process of estimation does not have to be onerous. Done right, it catalyzes the accomplishment of multiple projects.

There are several estimation metrics, and one such metric is story points. Story points is an estimation metric in agile frameworks used for gauging the effort involved in implementing a work item. Story points in Jira help in estimating the backlog work items during every sprint planning.

How do I setup Jira integration?

To hit the ground running with Jira integration in Ally.io, here's what you need to do:

  • From the navigation menu, click on Admin > select the Integrations tab.
  • Against Jira, you will have an option to Enable the integration. If a connection has been made previously or if the integration has been enabled already, you will have the option to Manage the enabled integration.
  • This integration can also be disabled from the same section by clicking on Change, and choosing Disable integration from the dropdown.

If you need additional help in setting up your connection, read our help article on Jira integration.

Track progress of key results in Ally.io by story points

The status of key results will be updated automatically depending on the story points completed in Jira.

  • While creating or editing a key result in Ally.io, choose the method using which you want to measure the progress — percent complete or KPI (success metric).

If you choose to measure progress by the complete percentage,

  • Click on Connect data source to auto-update progress. From the drop-down menu, select Jira.
  • If you have already created a connection, or if your administrator has shared a connection with you, that connection will be selected automatically. Ally.io will prompt you to create a new connection only if there are no connections created or shared.
  • Provide the JQL, and from the drop-down menu for tracking progress, select Story Points.
  • Click Next > Save.

If you choose to measure progress by the KPI metric,

  • The name of the metric will automatically be set as 'Story Points' if you choose to track the progress by story points. However, if you wish to have a different one, you can provide the name for the metric. Set a target value and starting value.
  • Click on Connect data source to auto-update progress. From the drop-down menu, select Jira.
  • If you have already created a connection, or if your administrator has shared a connection with you, that connection will be selected automatically. Ally.io will prompt you to create a new connection only if there are no connections created or shared.
  • Provide the JQL, and from the drop-down menu for tracking progress, select Story Points.
  • The checkbox for 'Count only done tickets' will be ticked by default. If you want to measure the progress of the key result by story points of the completed tickets in Jira, this option comes handy. However, if you want to measure the progress of the key result by story points of all the tickets pertaining to the JQL in Jira, irrespective of the completion status, you can uncheck the box.
  • Click Next > Save.

Track progress of projects in Ally.io by story points

The status of projects will be updated automatically depending on the story points completed in Jira.

  • While creating or editing a project in Ally.io, click on Select an option to add tasks to project. From the drop-down menu, select Jira.
  • If you have already created a connection, or if your administrator has shared a connection with you, that connection will be selected automatically. Ally.io will prompt you to create a new connection only if there are no connections created or shared.
  • Provide the JQL, and from the drop-down menu for tracking progress, select Story Points.
  • All the tasks associated with the JQL will be listed, along with additional task details — name, story points, assignee, and due date.
  • Click Next > Save.

Best practice

For Jira issues that do not have an estimation, the average of story points of the remaining issues in the specified JQL will be assigned automatically. As best practice, Ally.io sets the default value of story points for non-estimated Jira issues to the average value, and this will help in measuring the progress in a meaningful way than just using 0 as the default value.

Say, you have 3 issues, out of which 2 issues have the estimation as 4 story points and 5 story points respectively. If the third issue does not have a story point estimate, the default value will be average of story points of the other two issues, which would be 4.5.

Common questions

  1. Can I track progress by the custom fields in my Jira instance?

    Yes, you can track the progress of key results and projects in Ally.io by the custom field in your Jira instance. In addition to the metrics supported by Ally.io, you can bring any numeric custom field from Jira to measure the progress. To know more about using custom fields, read our article on Jira integration.
  2. What's the difference between story points and story point estimate?

    Jira has two types of service projects — classic and next-gen. The estimation on classic projects is story points, and the estimation on next-gen projects is story point estimate.


Did this answer your question?