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

0 votes
Answer 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 Sign up to answer
Community showcase
Published Feb 26, 2019 in Jira Software

How to prevent the propagation of unused project schemes, workflows & screens in Jira software

Atlassian ranks project attributes as the third most important factor impacting performance in the category of data. It’s not surprising, since project attributes are precisely the rules used to ma...

625 views 0 7
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