My team is using a Jira Kanban board (Kanban methodology as well) for managing the workflow (changes/incidents/spikes/tasks) of a 'mature' software product. When there are elements which require code changes in the 'Selected For Development' queue, it is straightforward to release them and make them show in the corresponding version. However, should spikes or tasks which don't require anything but investigation (and sometimes to reject the functionality proposed for investigation) also be included in releases?
2
-
What does it mean (to you) when a ticket is included in a release?– Bart van Ingen SchenauAug 29, 2022 at 10:57
-
@BartvanIngenSchenau in principle, that some code has been changed and deployed. Should I maybe enhance this definition to maintain consistency with other non-code related work?– Javi TorreAug 29, 2022 at 11:08
Add a comment
|
1 Answer
A spike can be done, whether a release is planned or not.
A release can be planned (and deployed) whether the spike is done or not.
So they are independent entities. It does not make any sense to include one in the other.
-
What column should I move my spike to when it is done? And how do I make it disappear from the board without deleting it and without including it in a release? Sep 8, 2022 at 11:09
-
I have no idea what your board looks like or how you have configured it. Don't you have a "done" column or state?– nvoigtSep 8, 2022 at 11:48
-
Yes, but stories will be showing in the done column until they are released. Sep 8, 2022 at 11:57
-
1Jira is super configurable. Talk to your Jira Administrator about your workflow and how to make that happen in Jira. Personally, I would just create another state that takes items off the board (maybe "completed without release"). Or you just create a dummy release for all the tickets you don't want to actually release, in case your administrator is too slow or doesn't want to make that change.– nvoigtSep 8, 2022 at 12:08