0

I am using Kanban methodology in Jira to manage the workflow of a 'mature' project. We can do deployments to production on Thursdays, so we accumulate stories in the 'Ready For Production' column until they go in a release, and then, after they are deployed, we hit the 'Release' button and create a new version. However, if, let's say we're on a Monday and something needs to be released urgently and we create an expedite swimlane, is there any way to release just that and not the other non-expedite tasks that are due to be released on Thursday?

enter image description here

9
  • How are you using the Jira fixVersion field in this workflow? You may need to look at the integration between Jira and your deployment tool(s), but if you release a specific version, you may be able to take advantage of the fixVersion field. You may also be able to take advantage of links between issues and deployments in your tools. But without knowing more about your integrations and how you are integrating your source control and deployment tools with Jira, it's hard to say.
    – Thomas Owens
    Aug 29 at 10:45
  • @ThomasOwens I am not integrating Jira and my deployment tool. And I am not using the fixversion field. How could I take advantage of that field for splitting releases?
    – Javi Torre
    Aug 29 at 11:07
  • @JaviTorre, how do you deal with the occasional story that was started but could not be (properly) finished before the release on Thursday? For example, work was started on Wednesday with the expectation to finish on time, but something happened and that expectation could not be met and the work is at best half finished. Aug 29 at 12:00
  • @BartvanIngenSchenau it remains in the 'In Development' column and not included for that release.
    – Javi Torre
    Aug 29 at 12:30
  • 1
    @JaviTorre Ah. I just poked around the docs and config - looks like someone turned that off in my instance, but I found it in the docs. I think I can write an answer now.
    – Thomas Owens
    Aug 29 at 15:55

1 Answer 1

2

When you click the "Release" button on a company-managed Kanban board, you are choosing from a list of versions that are allocated to issues in that column. When you don't have versions assigned to those issues, you would be releasing all of them.

If you set the Fix Version field in those issues appropriately, you will be able to release one version and mark the issues associated with that version as Released. It's not clear what happens if you have some issues with a manually set Fix Version and others with no Fix Version, so you may need to explicitly set the Fix Version of all of the issues in the column.

I would also recommend looking at your issue workflow in general and consider setting the Fix Version field in advance. You can unlock some good visualizations of progress toward a version and make sure the work that you expect to release is on track for completion throughout the development process.

2
  • Thanks! So, if I can mark an issue with a fix version that is already released, when moving it to the 'done' column, it will disappear from there, won't it?
    – Javi Torre
    Aug 29 at 16:29
  • 1
    @JaviTorre You may want to experiment with that a bit. It depends on how you have your Kanban board sub-filter set up (I have mine set to only include work in unreleased versions or an empty fix version, for example) or other configurations. There's quite a bit that plays off of the different configs - the states mapped to each column, your board queries, and a couple of other things.
    – Thomas Owens
    Aug 29 at 16:40

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.