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?
...PermissionsStartOnly=true User=www-data Group=www-data ExecStart=/opt/jira/bin/startup.sh ExecStop=/opt/jira/bin/shutdown.sh TimeoutStartSec=120 TimeoutStopSec=600 PrivateTmp=true [Install] WantedBy...
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!
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