It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

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

3 votes
Answer accepted

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.



thanks Pelle


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
Community showcase
Published in Halp

Halp - Conversational Ticketing Help Desk for internal requests

From the Halp Team Howdy!  👋   We’re Halp, a conversational ticketing help desk for all of your internal requests in Slack (and soon to be MS Teams!). We’re excited to be a par...

57 views 0 2
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you