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

Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Sarah Schuster
Posted Mar 28, 2018 in Jira Software

Can a company’s culture make or break agile adoption?

Can a new-to-agile team survive and thrive in a non-agile culture? If so, what advice would you give to those trying to be agile in a non-agile culture? What's the key(s) to success? Share your thoug...

13,183 views 15 13
Join discussion

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