Jira Assistant Issues

View #106 on GitHub to know more details

#106 - Worklog Report doesn't work on Brave when you delete Default User group

KirillZinchenko commented on Dec 03, 2019

Hi,

I just tried to move my workflow from Google Chrome to the Brave browser, but I encountered a bug with your extension.

When I am trying to check my Worklog - I can see only the blank page with a grey background.

Looks like I also found how to reproduce it.

  1. Go to User groups
  2. Delete your user from the Default group (or just delete group, I can't remember what I did before on this step)
  3. Save changes
  4. Go to Worklog report
  5. Try to see any report

Actual result: I can see a grey background only and have some errors in the browser console

I fixed the issue when I added myself to the Default group and saved changes. After that, I deleted myself and the default group again and everything is fine now.

I don't know if it's s Brave related issue only of maybe you can try to reproduce it in Google Chrome

My Jira Assistant version is 0.87

My Brave version is:

image

Here's Brave Console log:

4.c1b2bfbf.chunk.js:1 TypeError: Cannot read property 'total' of undefined
    at 3.87c8ef0f.chunk.js:1
    at Array.forEach (<anonymous>)
    at o.reduce.grandTotal (3.87c8ef0f.chunk.js:1)
    at Array.reduce (<anonymous>)
    at t.value (3.87c8ef0f.chunk.js:1)
    at new t (3.87c8ef0f.chunk.js:1)
    at _o (4.c1b2bfbf.chunk.js:1)
    at Xa (4.c1b2bfbf.chunk.js:1)
    at _l (4.c1b2bfbf.chunk.js:1)
    at _s (4.c1b2bfbf.chunk.js:1)
hl @ 4.c1b2bfbf.chunk.js:1
Dl.n.callback @ 4.c1b2bfbf.chunk.js:1
xo @ 4.c1b2bfbf.chunk.js:1
ko @ 4.c1b2bfbf.chunk.js:1
(anonymous) @ 4.c1b2bfbf.chunk.js:1
t.unstable_runWithPriority @ 4.c1b2bfbf.chunk.js:1
qi @ 4.c1b2bfbf.chunk.js:1
Ms @ 4.c1b2bfbf.chunk.js:1
gs @ 4.c1b2bfbf.chunk.js:1
(anonymous) @ 4.c1b2bfbf.chunk.js:1
t.unstable_runWithPriority @ 4.c1b2bfbf.chunk.js:1
qi @ 4.c1b2bfbf.chunk.js:1
Xi @ 4.c1b2bfbf.chunk.js:1
$i @ 4.c1b2bfbf.chunk.js:1
hs @ 4.c1b2bfbf.chunk.js:1
enqueueSetState @ 4.c1b2bfbf.chunk.js:1
w.setState @ 4.c1b2bfbf.chunk.js:1
(anonymous) @ 3.87c8ef0f.chunk.js:1
Promise.then (async)
a.refreshData @ 3.87c8ef0f.chunk.js:1
(anonymous) @ 4.c1b2bfbf.chunk.js:1
k @ 4.c1b2bfbf.chunk.js:1
(anonymous) @ 4.c1b2bfbf.chunk.js:1
S @ 4.c1b2bfbf.chunk.js:1
O @ 4.c1b2bfbf.chunk.js:1
T @ 4.c1b2bfbf.chunk.js:1
P @ 4.c1b2bfbf.chunk.js:1
Cn @ 4.c1b2bfbf.chunk.js:1
ue @ 4.c1b2bfbf.chunk.js:1
Tn @ 4.c1b2bfbf.chunk.js:1
On @ 4.c1b2bfbf.chunk.js:1
_n @ 4.c1b2bfbf.chunk.js:1
t.unstable_runWithPriority @ 4.c1b2bfbf.chunk.js:1
qi @ 4.c1b2bfbf.chunk.js:1
le @ 4.c1b2bfbf.chunk.js:1
(anonymous) @ 4.c1b2bfbf.chunk.js:1
index.027dead5.chunk.js:1 Unhandled rejection (promise:  Promise {<rejected>: TypeError: Cannot read property 'total' of undefined
    at chrome-extension://momjbjbjpbcbnepbgkki…} , reason:  TypeError: Cannot read property 'total' of undefined
    at 3.87c8ef0f.chunk.js:1
    at Array.forEach (<anonymous>)
    at o.reduce.grandTotal (3.87c8ef0f.chunk.js:1)
    at Array.reduce (<anonymous>)
    at t.value (3.87c8ef0f.chunk.js:1)
    at new t (3.87c8ef0f.chunk.js:1)
    at _o (4.c1b2bfbf.chunk.js:1)
    at Xa (4.c1b2bfbf.chunk.js:1)
    at _l (4.c1b2bfbf.chunk.js:1)
    at _s (4.c1b2bfbf.chunk.js:1) ).
value @ index.027dead5.chunk.js:1
(anonymous) @ index.027dead5.chunk.js:1
3.87c8ef0f.chunk.js:1 Uncaught (in promise) TypeError: Cannot read property 'total' of undefined
    at 3.87c8ef0f.chunk.js:1
    at Array.forEach (<anonymous>)
    at o.reduce.grandTotal (3.87c8ef0f.chunk.js:1)
    at Array.reduce (<anonymous>)
    at t.value (3.87c8ef0f.chunk.js:1)
    at new t (3.87c8ef0f.chunk.js:1)
    at _o (4.c1b2bfbf.chunk.js:1)
    at Xa (4.c1b2bfbf.chunk.js:1)
    at _l (4.c1b2bfbf.chunk.js:1)
    at _s (4.c1b2bfbf.chunk.js:1)

shridhar-tl commented on Dec 01, 2019

Hi @KirillZinchenko - I had fixed couple of issues in Worklog report and is available since Jira Assistant v0.88. Please retest it once your version gets updated and let me know if you still face this issue.

KirillZinchenko commented on Dec 03, 2019

@shridhar-tl hi, I will look into it and let you know, thanks

KirillZinchenko commented on Dec 03, 2019

Looks like the issue is fixed, at least I can't reproduce it anymore.

Thank you very much for your work, I will also send a little donation to your team later.

🟢