Forums

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

[solved] can't add work log to issues

T_ Hinze
May 4, 2026

Last week any user can add his work logs to the issues.

Since today our users can't add work log to issues. They can open the issue and click on "work log", then the modal dialog comes up and they put spent time and comment into the dialog. After click auf "save" nothing happends.

in the browser JS console I see this:

---

sentry.089cdfeb.js:2 Uncaught n: Invalid issueId - ari:cloud:jira:a3ba68ad-4b17-42e9-a4b5-5cbd27ef0d07:issue/44904, expected ID of format /^[0-9]+$/.
at chunk-S7RIZVFI.mjs:15:1
at chunk-S7RIZVFI.mjs:17:1
at Array.forEach (<anonymous>)
at o.fromOpts (chunk-S7RIZVFI.mjs:21:11)
at e.create (chunk-AD75JOJ7.mjs:46:7)
at BoardIssueView.tsx:206:26
at useIssueViewFieldUpdateEvents.tsx:125:47
at Array.forEach (<anonymous>)
at useIssueViewFieldUpdateEvents.tsx:125:35
at c (bind-actions.tsx:31:2)
at i.<computed> (bind-actions.tsx:70:2)
at Object.t [as onSubmit] (useSoftRefreshCallbacks.tsx:230:11)
at IssueViewTimeTrackingAddModal.tsx:848:6
at n.<computed>.o.<computed> (with-fire-ui-analytics.tsx:85:5)
at n.<computed>.o.<computed> (with-fire-ui-analytics.tsx:85:5)
at y (LogTimeModalWithValidation.tsx:299:4)
at Object.current (button-base.tsx:147:4)
at usePlatformLeafEventHandler.ts:70:8
at Object.eJ (react-dom.profiling.min.js:59:280)
at e5 (react-dom.profiling.min.js:60:169)
at react-dom.profiling.min.js:60:195
at nC (react-dom.profiling.min.js:60:259)
at nI (react-dom.profiling.min.js:110:151)
at react-dom.profiling.min.js:126:183
at lu (react-dom.profiling.min.js:291:470)
at eW (react-dom.profiling.min.js:58:72)
at nD (react-dom.profiling.min.js:117:39)
at rt (react-dom.profiling.min.js:81:33)
at t7 (react-dom.profiling.min.js:79:329)
at HTMLDivElement.a (sentry.089cdfeb.js:2:87800)

--- 

 

We dont have changed any thing on our Jira app or permissions and so on. 

I dont see that we canndo to fix this.
Need help.

Best regards

 

5 answers

1 vote
T_ Hinze
May 6, 2026

[SOLVED]

Today I received the feedback from Jira support, that the problem was fixed.

see also: https://jira-software.status.atlassian.com/incidents/h5692lfkkmgt

Miroslav Metruk
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 6, 2026

I confirm, now work log works also for me!

0 votes
Jaziel González
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 5, 2026

The issue is strictly limited to the Board View overlay/modal.

The console error clearly shows a type mismatch: the Board is passing an ARI (Atlassian Resource Identifier) while the Log Work component expects a Numeric ID.

0 votes
Miroslav Metruk
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 5, 2026

I am experiencing exactly the same behavior since today. Yesterday all was working. Today I can't add a work log.

Console:

sentry.fb133168.js:2 Uncaught n: Invalid issueId - ari:cloud:jira:2940a044-ceb0-4ac4-a2b3-afc1289fe18b:issue/12628, expected ID of format /^[0-9]+$/.
at chunk-S7RIZVFI.mjs:15:1
at chunk-S7RIZVFI.mjs:17:1
at Array.forEach (<anonymous>)
at i.fromOpts (chunk-S7RIZVFI.mjs:21:11)
at e.create (chunk-AD75JOJ7.mjs:46:7)
at BoardIssueView.tsx:206:26
at useIssueViewFieldUpdateEvents.tsx:125:47
at Array.forEach (<anonymous>)
at useIssueViewFieldUpdateEvents.tsx:125:35
at c (bind-actions.tsx:31:2)
at i.<computed> (bind-actions.tsx:70:2)
at Object.t [as onSubmit] (useSoftRefreshCallbacks.tsx:230:11)
at IssueViewTimeTrackingAddModal.tsx:848:6
at s.<computed>.i.<computed> (with-fire-ui-analytics.tsx:85:5)
at s.<computed>.i.<computed> (with-fire-ui-analytics.tsx:85:5)
at y (LogTimeModalWithValidation.tsx:299:4)
at Object.current (button-base.tsx:147:4)
at usePlatformLeafEventHandler.ts:70:8
at Object.eJ (react-dom.profiling.min.js:59:280)
at e5 (react-dom.profiling.min.js:60:169)
at react-dom.profiling.min.js:60:195
at nC (react-dom.profiling.min.js:60:259)
at nI (react-dom.profiling.min.js:110:151)
at react-dom.profiling.min.js:126:183
at lu (react-dom.profiling.min.js:291:470)
at eW (react-dom.profiling.min.js:58:72)
at nD (react-dom.profiling.min.js:117:39)
at rt (react-dom.profiling.min.js:81:33)
at t7 (react-dom.profiling.min.js:79:329)
at HTMLDivElement.a (sentry.fb133168.js:2:87800)
(anonymous) @ chunk-S7RIZVFI.mjs:15
(anonymous) @ chunk-S7RIZVFI.mjs:17
fromOpts @ chunk-S7RIZVFI.mjs:21
create @ chunk-AD75JOJ7.mjs:46
(anonymous) @ BoardIssueView.tsx:206
(anonymous) @ useIssueViewFieldUpdateEvents.tsx:125
FIELD_CHANGE_FAILED @ useIssueViewFieldUpdateEvents.tsx:125
(anonymous) @ bind-actions.tsx:31
(anonymous) @ bind-actions.tsx:70
(anonymous) @ useSoftRefreshCallbacks.tsx:230
env @ IssueViewTimeTrackingAddModal.tsx:848
(anonymous) @ with-fire-ui-analytics.tsx:85
(anonymous) @ with-fire-ui-analytics.tsx:85
(anonymous) @ LogTimeModalWithValidation.tsx:299
useContext @ button-base.tsx:147
(anonymous) @ usePlatformLeafEventHandler.ts:70
eJ @ react-dom.profiling.min.js:59
e5 @ react-dom.profiling.min.js:60
(anonymous) @ react-dom.profiling.min.js:60
nC @ react-dom.profiling.min.js:60
nI @ react-dom.profiling.min.js:110
(anonymous) @ react-dom.profiling.min.js:126
lu @ react-dom.profiling.min.js:291
eW @ react-dom.profiling.min.js:58
nD @ react-dom.profiling.min.js:117
rt @ react-dom.profiling.min.js:81
t7 @ react-dom.profiling.min.js:79
a @ sentry.fb133168.js:2

Tracking Prevention blocked access to storage for <URL>.
Tracking Prevention blocked access to storage for <URL>.
Tracking Prevention blocked access to storage for <URL>.
Tracking Prevention blocked access to storage for <URL>.
Tracking Prevention blocked access to storage for <URL>.
Tracking Prevention blocked access to storage for <URL>.
Tracking Prevention blocked access to storage for <URL>.
Tracking Prevention blocked access to storage for <URL>.
sentry.fb133168.js:2 error while parsing a build key Error: Invalid build key
at i (index.tsx:41:3)
at r (index.tsx:80:15)
at utils.ts:14:2
at n (utils.ts:53:2)
at index.ts:27:50
at Array.every (<anonymous>)
at index.ts:27:9
at Array.reduce (<anonymous>)
at index.ts:22:4
at c (bind-actions.tsx:31:2)
at i.<computed> (bind-actions.tsx:70:2)
at c.onRemoteActionsUpdate (index.ts:30:3)
at c.fetchRemoteActions (index.tsx:100:12)
(anonymous) @ sentry.fb133168.js:2
(anonymous) @ utils.ts:40
(anonymous) @ utils.ts:53
(anonymous) @ index.ts:27
(anonymous) @ index.ts:27
(anonymous) @ index.ts:22
(anonymous) @ bind-actions.tsx:31
(anonymous) @ bind-actions.tsx:70
(anonymous) @ index.ts:30
fetchRemoteActions @ index.tsx:100
await in fetchRemoteActions
start @ index.tsx:119
onActive @ index.tsx:78
(anonymous) @ browser-interaction-time.ts:132
(anonymous) @ browser-interaction-time.ts:129
(anonymous) @ browser-interaction-time.ts:137
(anonymous) @ helpers.ts:86
sentry.fb133168.js:2 error while parsing a build key Error: Invalid build key
at i (index.tsx:41:3)
at r (index.tsx:80:15)
at utils.ts:14:2
at n (utils.ts:53:2)
at index.ts:27:50
at Array.every (<anonymous>)
at index.ts:27:9
at Array.reduce (<anonymous>)
at index.ts:22:4
at c (bind-actions.tsx:31:2)
at i.<computed> (bind-actions.tsx:70:2)
at c.onRemoteActionsUpdate (index.ts:30:3)
at c.fetchRemoteActions (index.tsx:100:12)
(anonymous) @ sentry.fb133168.js:2
(anonymous) @ utils.ts:40
(anonymous) @ utils.ts:53
(anonymous) @ index.ts:27
(anonymous) @ index.ts:27
(anonymous) @ index.ts:22
(anonymous) @ bind-actions.tsx:31
(anonymous) @ bind-actions.tsx:70
(anonymous) @ index.ts:30
fetchRemoteActions @ index.tsx:100
await in fetchRemoteActions
start @ index.tsx:119
onActive @ index.tsx:78
(anonymous) @ browser-interaction-time.ts:132
(anonymous) @ browser-interaction-time.ts:129
(anonymous) @ browser-interaction-time.ts:137
(anonymous) @ helpers.ts:86
sentry.fb133168.js:2 error while parsing a build key Error: Invalid build key
at i (index.tsx:41:3)
at r (index.tsx:80:15)
at utils.ts:14:2
at n (utils.ts:53:2)
at index.ts:27:50
at Array.every (<anonymous>)
at index.ts:27:9
at Array.reduce (<anonymous>)
at index.ts:22:4
at c (bind-actions.tsx:31:2)
at i.<computed> (bind-actions.tsx:70:2)
at c.onRemoteActionsUpdate (index.ts:30:3)
at c.fetchRemoteActions (index.tsx:100:12)
(anonymous) @ sentry.fb133168.js:2
(anonymous) @ utils.ts:40
(anonymous) @ utils.ts:53
(anonymous) @ index.ts:27
(anonymous) @ index.ts:27
(anonymous) @ index.ts:22
(anonymous) @ bind-actions.tsx:31
(anonymous) @ bind-actions.tsx:70
(anonymous) @ index.ts:30
fetchRemoteActions @ index.tsx:100
await in fetchRemoteActions
start @ index.tsx:119
onActive @ index.tsx:78
(anonymous) @ browser-interaction-time.ts:132
(anonymous) @ browser-interaction-time.ts:129
(anonymous) @ browser-interaction-time.ts:137
(anonymous) @ helpers.ts:86
sentry.fb133168.js:2 error while parsing a build key Error: Invalid build key
at i (index.tsx:41:3)
at r (index.tsx:80:15)
at utils.ts:14:2
at n (utils.ts:53:2)
at index.ts:27:50
at Array.every (<anonymous>)
at index.ts:27:9
at Array.reduce (<anonymous>)
at index.ts:22:4
at c (bind-actions.tsx:31:2)
at i.<computed> (bind-actions.tsx:70:2)
at c.onRemoteActionsUpdate (index.ts:30:3)
at c.fetchRemoteActions (index.tsx:100:12)
(anonymous) @ sentry.fb133168.js:2
(anonymous) @ utils.ts:40
(anonymous) @ utils.ts:53
(anonymous) @ index.ts:27
(anonymous) @ index.ts:27
(anonymous) @ index.ts:22
(anonymous) @ bind-actions.tsx:31
(anonymous) @ bind-actions.tsx:70
(anonymous) @ index.ts:30
fetchRemoteActions @ index.tsx:100
await in fetchRemoteActions
start @ index.tsx:119
onActive @ index.tsx:78
(anonymous) @ browser-interaction-time.ts:132
(anonymous) @ browser-interaction-time.ts:129
(anonymous) @ browser-interaction-time.ts:137
(anonymous) @ helpers.ts:86
sentry.fb133168.js:2 error while parsing a build key Error: Invalid build key
at i (index.tsx:41:3)
at r (index.tsx:80:15)
at utils.ts:14:2
at n (utils.ts:53:2)
at index.ts:27:50
at Array.every (<anonymous>)
at index.ts:27:9
at Array.reduce (<anonymous>)
at index.ts:22:4
at c (bind-actions.tsx:31:2)
at i.<computed> (bind-actions.tsx:70:2)
at c.onRemoteActionsUpdate (index.ts:30:3)
at c.fetchRemoteActions (index.tsx:100:12)
(anonymous) @ sentry.fb133168.js:2
(anonymous) @ utils.ts:40
(anonymous) @ utils.ts:53
(anonymous) @ index.ts:27
(anonymous) @ index.ts:27
(anonymous) @ index.ts:22
(anonymous) @ bind-actions.tsx:31
(anonymous) @ bind-actions.tsx:70
(anonymous) @ index.ts:30
fetchRemoteActions @ index.tsx:100
await in fetchRemoteActions
start @ index.tsx:119
onActive @ index.tsx:78
(anonymous) @ browser-interaction-time.ts:132
(anonymous) @ browser-interaction-time.ts:129
(anonymous) @ browser-interaction-time.ts:137
(anonymous) @ helpers.ts:86
sentry.fb133168.js:2 error while parsing a build key Error: Invalid build key
at i (index.tsx:41:3)
at r (index.tsx:80:15)
at utils.ts:14:2
at n (utils.ts:53:2)
at index.ts:27:50
at Array.every (<anonymous>)
at index.ts:27:9
at Array.reduce (<anonymous>)
at index.ts:22:4
at c (bind-actions.tsx:31:2)
at i.<computed> (bind-actions.tsx:70:2)
at c.onRemoteActionsUpdate (index.ts:30:3)
at c.fetchRemoteActions (index.tsx:100:12)
(anonymous) @ sentry.fb133168.js:2
(anonymous) @ utils.ts:40
(anonymous) @ utils.ts:53
(anonymous) @ index.ts:27
(anonymous) @ index.ts:27
(anonymous) @ index.ts:22
(anonymous) @ bind-actions.tsx:31
(anonymous) @ bind-actions.tsx:70
(anonymous) @ index.ts:30
fetchRemoteActions @ index.tsx:100
await in fetchRemoteActions
start @ index.tsx:119
onActive @ index.tsx:78
(anonymous) @ browser-interaction-time.ts:132
(anonymous) @ browser-interaction-time.ts:129
(anonymous) @ browser-interaction-time.ts:137
(anonymous) @ helpers.ts:86
sentry.fb133168.js:2 error while parsing a build key Error: Invalid build key
at i (index.tsx:41:3)
at r (index.tsx:80:15)
at utils.ts:14:2
at n (utils.ts:53:2)
at index.ts:27:50
at Array.every (<anonymous>)
at index.ts:27:9
at Array.reduce (<anonymous>)
at index.ts:22:4
at c (bind-actions.tsx:31:2)
at i.<computed> (bind-actions.tsx:70:2)
at c.onRemoteActionsUpdate (index.ts:30:3)
at c.fetchRemoteActions (index.tsx:100:12)
(anonymous) @ sentry.fb133168.js:2
(anonymous) @ utils.ts:40
(anonymous) @ utils.ts:53
(anonymous) @ index.ts:27
(anonymous) @ index.ts:27
(anonymous) @ index.ts:22
(anonymous) @ bind-actions.tsx:31
(anonymous) @ bind-actions.tsx:70
(anonymous) @ index.ts:30
fetchRemoteActions @ index.tsx:100
await in fetchRemoteActions
start @ index.tsx:119
onActive @ index.tsx:78
(anonymous) @ browser-interaction-time.ts:132
(anonymous) @ browser-interaction-time.ts:129
(anonymous) @ browser-interaction-time.ts:137
(anonymous) @ helpers.ts:86

T_ Hinze
May 5, 2026

For your information:

 

I had add an support ticket yesterday with all the details.

I hope the developer can fix this issue quickly.

Like Miroslav Metruk likes this
0 votes
T_ Hinze
May 4, 2026

In the browser console I see this error after loading the page without any interaction:

sentry.089cdfeb.js:2 Uncaught (in promise) TypeError: e.update is not a function at e.captureSession (sentry.089cdfeb.js:2:29526) at o._sendSessionUpdate (shared~vendor~ar.4140b4d4.js:5:1048) at o.endSession (shared~vendor~ar.4140b4d4.js:5:383) at o.startSession (shared~vendor~ar.4140b4d4.js:5:816) at f (sentry.089cdfeb.js:2:94260) at sentry.089cdfeb.js:2:93253 at Object.i (sentry.089cdfeb.js:2:93397) at l (index.ts:104:6)

This error accours multiple times (4-5 x).

The console AI explain this error:

"Explanation

This error occurs within the Sentry SDK. The stack trace and code snippet show that e.captureSession is being called with an argument e (representing a Session object) that is expected to have an .update() method, but that method is missing.

This usually happens due to a version mismatch or dependency conflict between different Sentry packages (e.g., @Sentry/browser@Sentry/hub, or @Sentry/react). In Sentry's internal logic, the Hub or Client is passing a session object that doesn't match the interface expected by the captureSession implementation. Specifically, if one part of your application uses an older version of the SDK while another uses a newer one, the session object structure may differ."

I think, the problem should not be on my side.

0 votes
Nikola Perisic
Community Champion
May 4, 2026

Welcome @T_ Hinze 

You've checked the Work on issues permission in your space permission scheme?

T_ Hinze
May 4, 2026

Yes. In very rare situations I can log work, but at the 2nd try I can't. 

I think this is not a permission problem, but I dont know how to catch the problem reason.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events