nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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

Fabian Meier1

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!

https://jira.atlassian.com/browse/GHS-6713

https://jira.atlassian.com/browse/GHS-5397

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?

Thanks!

Accepted answers

Fabian Meier1

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

swimlane_with_status

Done via patching the SwimlaneView.soy template file (\includes\js\rapid\ui\work\SwimlaneView.soy).

All comments

Fabian Meier1

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

swimlane_with_status

Done via patching the SwimlaneView.soy template file (\includes\js\rapid\ui\work\SwimlaneView.soy).

Dave Anderson

Kudos!

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

Thanks, d.

MattS

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

Fabian Meier1

I already posted it in the GHS Ticket: https://jira.atlassian.com/browse/GHS-6713

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira-software

jira-administration