Easiest way would be to call the spike a Story.
You could also create a new Spike type and give it the same fields and workflows as a Story.
To me, a spike is either anticipated in which case the work involved should be incorporated into the Story it is related to - or it is not anticipated in which case the work involved is overhead such as a bug fix. Personally, I'd call it a Task and not give it Story Points, but ultimately that's up to you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.