Can we track more than one velocity metric in one sprint (e.g. story points and time)?

[Paul Sobocinski]

From my experience, story points work best for user stories. So what about other issue types? In past teams (and the current one), we've had success with time-boxes, especially for "spike solution" tickets. However we're experimenting with time-boxes for ticket types such as tasks (and potentially, bugs).

Is there a way to track a second velocity metric in Jira (in our case, a time-based one)?

Also, what are peoples' opinions on such a practice? Any comments / concerns?

[Raimundas Juska]

I am not sure if you can track more than one metric in Jira's built-in velocity report. However, you can do this via apps - https://marketplace.atlassian.com/apps/1219761/individual-velocity-report-chart-gadget?hosting=cloud&tab=overview

Disclosure - I am the developer of this app.

[Paul Sobocinski]

So if I used the gadget that you linked above, I can tell it to use a custom field that we've configured (in our case "timebox), and then track / measure velocity of that metric in the gadget?

[Raimundas Juska]

Unfortunately only regular time spent / original estimate fields are supported for time tracking.