Kanban Board column, single transition available, no transition title

[Kevin Mowrey]

Hello,

First a little context around my question: 

https://confluence.atlassian.com/jirasoftwarecloud/transitioning-an-issue-777002790.html

It says:

"If the target column is associated with more than one status, when you hover the issue over that column, each possible transition will appear as a separate section with a dashed outline. "

My question is: If the target column is associated with a single status, is there a way for the transition name to still appear?

Kevin

[Jack Brickey]

What appears is the Kanban column if there is more than a single status mapped to the column is not the transition name but the actual status name. However, this only appears if there is more than one status in order to distinguish between them.

[Kevin Mowrey]

Thanks Jack. Two things:

1) what appears in our version is the transition name, not the status. (see attached)

2) What I'm asking is whether there is a way to have the transition name (or perhaps in your case, the status name) appear even if there is only one transition/status in the Kanban column

[Jack Brickey]

Thanks for the clarification. I was obviously mistaken here. Not sure if I recalled incorrectly or it changed, but no matter. In any event, no it is not possible. One option is to create a fully configurable Kanban in lieu of the default and title the columns to your needs.

[Kevin Mowrey]

Thanks Jack. I was worried that this might be the case. The workflow we're working with here is fully custom. Renaming the columns in the KanBan has been done, but it isn't quite sufficient. 

What we've got is a (I'll go ahead and say) very complex workflow that travels through an Active status multiple times. Rather than have multiple versions on an Active status, we're essentially progressing the linear state of the issue through a customer field and this allows users to still understand where it is in the overall process, despite being in the same "Active" status throughout the overall process. The same is occurring with a couple other columns on our KanBan board. The columns are generically named, but the transitions that appear in each differ depending on the 'state' of the issue. The one problem we're finding with this (imo kind of cool) solution, is that when there is only one transition available in the column, it is not easily seen what transition it is that is about to be executed by dropping it into the column. 

Shucks. 

:)