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; } } }

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

Doug Varn2

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?

Accepted answers

pkirkeby

Hey Doug,

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

https://confluence.atlassian.com/display/GHKB/Unable+to+set+issues+to+Resolved+using+Greenhopper+Simplified+Workflow

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

Cheers,

Pelle

All comments

pkirkeby

Hey Doug,

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

https://confluence.atlassian.com/display/GHKB/Unable+to+set+issues+to+Resolved+using+Greenhopper+Simplified+Workflow

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

Cheers,

Pelle

Doug Varn2

thanks Pelle

JT4

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

Welcome!

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

Quick Links

Find more posts tagged with

jira-software

strikethrough