azure-boards-estimate
azure-boards-estimate copied to clipboard
Clicking Reveal button fails to show results
Clicking Reveal simply turns the screen blank and no results are shown.
It appears to be limited to a single story. The only thing unique about that one is that it has 2 votes, one from me and the other from another user.
Do you have an error on the console?
No, it just goes blank.
Just to be sure, I meant the console in the browser dev tools (F12). Nothing there?
Do you know what the two votes were?
Ah, sorry for my misunderstanding. Here are the two errors:
TypeError: Cannot read property 'identifier' of undefined at t.n.renderCard (main.b08896b5.chunk.js:1) at main.b08896b5.chunk.js:1 at Array.map (<anonymous>) at t.value (main.b08896b5.chunk.js:1) at Oi (1.d362811c.chunk.js:1) at Pi (1.d362811c.chunk.js:1) at Di (1.d362811c.chunk.js:1) at Ka (1.d362811c.chunk.js:1) at Ga (1.d362811c.chunk.js:1) at Os (1.d362811c.chunk.js:1) da @ 1.d362811c.chunk.js:1 n.callback @ 1.d362811c.chunk.js:1 oa @ 1.d362811c.chunk.js:1 ra @ 1.d362811c.chunk.js:1 za @ 1.d362811c.chunk.js:1 qa @ 1.d362811c.chunk.js:1 (anonymous) @ 1.d362811c.chunk.js:1 t.unstable_runWithPriority @ 1.d362811c.chunk.js:1 Rs @ 1.d362811c.chunk.js:1 Os @ 1.d362811c.chunk.js:1 Ts @ 1.d362811c.chunk.js:1 Ns @ 1.d362811c.chunk.js:1 kn @ 1.d362811c.chunk.js:1
Uncaught TypeError: Cannot read property 'identifier' of undefined at t.n.renderCard (main.b08896b5.chunk.js:1) at main.b08896b5.chunk.js:1 at Array.map (<anonymous>) at t.value (main.b08896b5.chunk.js:1) at Oi (1.d362811c.chunk.js:1) at Pi (1.d362811c.chunk.js:1) at Di (1.d362811c.chunk.js:1) at Ka (1.d362811c.chunk.js:1) at Ga (1.d362811c.chunk.js:1) at Os (1.d362811c.chunk.js:1) n.renderCard @ main.b08896b5.chunk.js:1 (anonymous) @ main.b08896b5.chunk.js:1 value @ main.b08896b5.chunk.js:1 Oi @ 1.d362811c.chunk.js:1 Pi @ 1.d362811c.chunk.js:1 Di @ 1.d362811c.chunk.js:1 Ka @ 1.d362811c.chunk.js:1 Ga @ 1.d362811c.chunk.js:1 Os @ 1.d362811c.chunk.js:1 Ts @ 1.d362811c.chunk.js:1 Ns @ 1.d362811c.chunk.js:1 kn @ 1.d362811c.chunk.js:1
Okay that helps, let me try if I can see when we'd end up in this case.
FYI - I looked into this a bit more and found something. Upon inspecting the code, I could see that the value for the card is visible in the source. In which case, I found that one card had no value and the other had a value of 'S', as we are using shirt size estimates. Not sure why one is blank, but guessing that is what is happening here:
Blank card:
<div class="card--frame card--back disabled" style="width: 50px; height: 75px; line-height: 74px; font-size: 24px;"></div>
S card:
<div class="card--frame card--back disabled" style="width: 50px; height: 75px; line-height: 74px; font-size: 24px;">S</div>
We ran into this today and what we found was that all devs were showing that they had estimated yet one of them informed us he did not. When he went to the page under 'All votes' an unrevealed card was displayed for him yet his vote was null (not selected). Even after he selected the card and we tried to reveal we still had the same issue. We were doing an offline estimation so realtime updates my not have been working fully at the time.
FYI - I looked into this a bit more and found something. Upon inspecting the code, I could see that the value for the card is visible in the source. In which case, I found that one card had no value and the other had a value of 'S', as we are using shirt size estimates.
I just encountered this issue, and found the same thing. One person had a card visible, but no actual estimate in the div contents.
In my case the person wasn't even a member of my team. I don't know whether he entered our estimation session and exited without selecting a card, or if some other quirk is causing him to show up in the voting results.
I have this issue too but only intermittently - I can't seem to find a pattern or cause as to when it happens.
Is there any update on a fix for this?
Link to original issue raised with devcommunity
Sorry, I don't see this bug and create #112 with screen of bug and suggest a solution
Okay that helps, let me try if I can see when we'd end up in this case.
@cschleiden @deeboe77 My team is currently experiencing this problem. Do we have an update on fixing this?