microsoft / azure-boards-estimate

MIT License
33 stars 24 forks source link

Empty screen if starting a new session via work item context menu #221

Closed Fbie18 closed 1 year ago

Fbie18 commented 1 year ago

If I want to start a new estimate session via the work item context menu it shows an empty screen.

Screen shot Screen shot

ssteiner1 commented 1 year ago

We are also facing this issue. Following for updates. Thanks!

pjonestt commented 1 year ago

Same issue, seems to have started recently: image

AminTi commented 1 year ago

Thanks for reporting, can you describe your environment?

chuac commented 1 year ago

Hi @AminTi, we're also facing the same issue.

I'm using: Microsoft Edge Version 110.0.1587.57 (Official build) (64-bit)

Fbie18 commented 1 year ago

Thanks for reporting, can you describe your environment?

@AminTi , what do you mean with "describe your environment"? What information are you looking for?

AminTi commented 1 year ago

I mean Azure environment. example onprem server2019. can you see any error in the console or network log in the browser (using F12, debug tools)?

Fbie18 commented 1 year ago

We are using Azure DevOps Services. Screen shot 3

AminTi commented 1 year ago

I can not reproduce the issues can we do a web session?

Arcade-Dev commented 1 year ago

We experience the same issue - adding from the backlog does not work and results in empty screen. image

AminTi commented 1 year ago

Hi can you uninstall the extension and install it again

GenesisMRainer commented 1 year ago

I am having the same issue. I tried both Chrome and Edge. I uninstalled and reinstalled the extension. Still an issue.

triciamunro commented 1 year ago

Same issue, using Firefox or Chrome. Started happening within the last week. Lots of warnings in the Console. Only error is: image

unholyranger-work commented 1 year ago

It looks like your URL is being encoded which may make it related to this issue: https://github.com/microsoft/azure-boards-estimate/issues/220

akamud commented 1 year ago

It looks like your URL is being encoded which may make it related to this issue: #220

This was my case. Changing the encoded values worked.

AminTi commented 1 year ago

Hi! guys I just released an update now it should be fixed.

dbarbary commented 1 year ago

hmm sorry. I just submitted this bug again. not seeing this as closed. I dont believe it is fixed. at least not in our environment. our environment is using version 2.3.82

TanjaPGGM commented 1 year ago

We're also still having issues. Going to 'Estimate work item(s)' now sends us to the Sessions overview, not to an estimation session for the selected work item(s).

dswindell commented 1 year ago

We are experiencing the same issue at our company: Right-clicking one or more backlog items from a backlog view and selecting “Estimate work item(s)” used to create an estimation session. Now when selecting “Estimate work item(s)” option, it loads the estimation page but with no session created, it simply shows a blank page at the URL.

triciamunro commented 1 year ago

Agree with the last comment, the issue is not resolved but the behavior is different. We have discovered a workaround: Create a query that returns the stories you want to groom, then, from the Estimate page create a query-based session. This is more tedious but at least you can create an estimation session. Here's the error in the Console now when you try to create a session by clicking on selected user stories: image

unholyranger-work commented 1 year ago

As our linked issue https://github.com/microsoft/azure-boards-estimate/issues/220, my team uses Query-based sessions. The annoying part is we cannot direct link to them and you cannot refresh the page else you go to the root of the extension; which is often necessary if tickets change or we have to resync our session with everyone. You also can not click on a ticket and then navigate back.

AminTi commented 1 year ago

I just released an update now, it should work

sergey-litvinov commented 1 year ago

@AminTi thanks! looks like it helped for our case when we copy paste the existing link and it works now fine.

dswindell commented 1 year ago

I tested and confirmed it is working as expected. Thank you AminTI!