How to add more context to KanBan swimlanes

[jasper.hoevenaars]

Hello!

I'm configuring a KanBan board for the team I'm in. We've defined all phases on the board and the swim lanes are configured per feature. However our over arching structure is:

 - Capability

    - Feature

        - Story

Since the feature field is by default on the card, we would like to make the swim lanes the capability that the story falls under, but we didn't find a straight forward way to do that yet. What would be a way to do this, or otherwise implement the Capability context in our KanBan board?

In this case, I would like this row/swimlane to show the capability this feature is attached to for example. Or otherwise configure one of the fields on the card to show the capability.

[Scott Theus · Accepted solution]

Hi Vasco,

I don't see how this could be accomplished; the issue IDs are created when the issue is created based on the project key and the next number in the sequence. Since you can't link an issue to another until both are created the issue ID for both will already be assigned. 

I can think of all sorts of confusion with modifying the issue IDs when links are added. What are you trying to accomplish? Perhaps there is another way.

-Scott

[Danyal Iqbal · Accepted solution]

No. Do you expect the ID (issueKey) of the linked issue to change in retrospect? That would be severely restrictive.

There are other ways to show this relationship e.g by adding the linked issue key to the summary in restrospect with a webservice/listener/postfunction.