How to Create a Spike in Jira
By Impran M N
A spike is a time-boxed research task used when a team needs to investigate something before they can properly estimate or plan a piece of work. This guide covers how to create and track a spike as an issue in Jira.
01Decide if a spike is the right issue type
Spikes are typically used when there's too much uncertainty to estimate a story accurately, and the team needs dedicated time to research or prototype first.
02Create a new issue
Start a new issue in your Jira project, since most teams don't have a built-in 'Spike' issue type by default.
03Label or type it as a spike
Use a label, custom issue type, or naming convention to mark the issue clearly as a spike so it's distinguishable from regular stories.
04Define the time box
Set a clear time limit for the investigation in the issue description, since a spike is meant to be bounded rather than open-ended.
05Document findings when complete
Once the research is done, record the outcome on the issue so the team can use it to estimate or plan the follow-up work.
Frequently asked questions
Does Jira have a built-in spike issue type?
Not by default in most configurations, so teams commonly create a custom issue type or use a label to track spikes.
How is a spike different from a regular story?
A spike is focused on research or investigation rather than delivering a feature, and it's meant to inform estimation on future work.
Should a spike be included in sprint velocity?
Practices vary by team, but many teams choose not to count spike effort toward velocity since it's investigative rather than delivery work.
What happens after a spike is finished?
The findings typically feed into creating or refining a related story, which can then be estimated more accurately.
Watch the full walkthrough
The same steps, demonstrated on screen from start to finish.



