Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Scrumboard in Greenhopper since latest update won't strike through finished stories

C_ Faysal_CFcon_
Atlassian Partner
May 16, 2013

the user who contacted me with this incident promises me it worked before.

steps to reproduce:

  1. use Greenhopper (most recent Version)
  2. create Scrum-based board
  3. create a story and some child-tasks
  4. put the story in a sprint (and start sprint)
  5. finish all tasks (set resolved)
  6. finish story (move to resolved,done or whatever...)

WORK-Mode

you will see the story in Work-Mode unstrikedout key-id among any other stories...

if you collapse it you can see child tasks in the correct column striked-out

PLAN-Mode

Story key-id is striked-out correctly on resolved stories

can someone please verify or tell me hints to resolve this irritating issue?

2 answers

1 accepted

1 vote
Answer accepted
AhmadDanial
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 16, 2013

Hey there, C. Faysal.

Tested a couple of times and I managed to confirm on this unexpected behavior. I have lodged a bug report to this:

Warm regards,

Danial

AhmadDanial
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 16, 2013

You are most welcome. Hopefully the devs will look into this matter real soon!

Warm regards,

Danial

C_ Faysal_CFcon_
Atlassian Partner
May 16, 2013
Glad you made it. Already created one at SAC. Thank you very much
0 votes
Jeison
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 16, 2013

Hey there! I followed your steps, but am unable to replicate it. It works fine for me. Can you try and reproduce it in another board? Even better if you test with a project that makes use of a different workflow.

C_ Faysal_CFcon_
Atlassian Partner
May 16, 2013
Hmm strange. Ok i will test on tuesday. Today i tested on 2 different instances with different projects and workflows. Swimlanes are set to stories in your test too right?

Suggest an answer

Log in or Sign up to answer