Does custom workflow prevent GH from striking out closed stories and tasks?

We recently changed our workflow to a custom one (rather than default). All stories and sub-tasks both end with the same old "Closed" state. Stories and sub-tasks do have different workflows in our model.

What we're finding is that Greenhopper no longer strikes out the Story ID on the task board (Work panel) once either sub tasks or stories become closed.

Any idea why this is?

1 answer

1 accepted

This widget could not be displayed.

Hey Doug,

It sounds like you need to configure the workflow to set the 'Resolution' field as explained here:

If the 'Resolution' field is set to Unresolved the strikethrough won't occur even if the 'Status' is set to Done.




We are having ths same issue on our boards. We do not use the simplified workflow.

The Resolution field is a required field in our workflow and does contain a value. The subtasks are displaying as expected, but the Stories no longer have the strike-through.

The board is configured to use the Story as a swim lane. We are using GH v6.2.1

Suggest an answer

Log in or Sign up to answer
Atlassian Summit 2018

Meet the community IRL

Atlassian Summit is an excellent opportunity for in-person support, training, and networking.

Learn more
Community showcase
Posted 3 hours ago in Teamwork

What teamwork quotes inspire you?

Hey everyone! My name is Natalie and I'm an editor of the Atlassian Blog and I've got a question for you: What's your favorite quote about teamwork?  We've compiled a list here, along with...

14 views 0 4
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