Any way of showing status of stories when using swimlanes per stories?

It is a limitation of Greenhopper that the status of the story in the swimlane header is not being shown. If oyu ask me, that is complete nonsense, because like this you make users actually leave the story in the status Open until they finished the last sub-task and being asked if they want to close it. Not agile at all!

I have already commented in those tickets, but you know Atlassian, they won't even look at it until it has a large amount of votes. (btw. that's not my definition of business value)

So here I am hunting for a solution. Is there any way of changing the templates to include the issue.status maybe as text behind the summary?


2 answers

1 accepted

Where there's a will there's a way:


Done via patching the template file (\includes\js\rapid\ui\work\


For n00bs like me, could you please post the modified & show the diff?

Thanks, d.

I guess the Agile jar has to be unpacked, the template modded and then the jar repacked too

I already posted it in the GHS Ticket:

Suggest an answer

Log in or Join to answer
Community showcase
Teodora [Botron]
Published Thursday in Marketplace Apps

Jira Inferno: The Nine Circles of Jira Administration Hell

If you spend enough time as a Jira admin - whether you are managing a single, mid-sized instance, a large enterprise one or juggling multiple instances at once - you will eventually find yourself in ...

445 views 1 15
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot