We have a workflow rule that says we need to assign a user when changing the story status to Assigned, but it doesn't show the assign modal anymore, it is just loading forever.
The dropdown with the Jira status is just loading forever.
Hi Andreas,
Can you try in other browser? Maybe is something regarding the browser.
I was using Chrome and that it just crashing before it even shows the modal. But in Firefox it shows the assign user modal, but it doesn't do anything even when I submit.
Even though it seems like it is requesting this:
POST: https://accutics.atlassian.net/secure/CommentAssignIssue.jspa
with a status 200, but with response content type set to HTML and empty?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Can you please try this once.
Reload the page:
Refresh the browser page after assigning the issue or modifying permissions. After that, the dropdown or modal ought to load properly.
Verify the conditions of the workflow:
Before launching the status dropdown, confirm that all necessary prerequisites are satisfied, such as having an assignee.
To avoid UI blockage, streamline or modify workflow conditions if at all possible.
Verify the permissions:
Verify that the user is authorized to handle "Transition Issues" for the project and status in question.
To confirm the user's access for the issue, utilize Jira's Permission Helper.
A user should be assigned the problem prior to attempting to modify the status to "Assigned." After that, attempt the transition once more after refreshing.
Hope this helps!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The workflow setup shouldn't be the problem, because that has always been working, and hasn't been changed for a loooong time.
When I look at the console then I see a lot of critical errors: example is:
Uncaught TypeError: r.once is not a function
at Object.<anonymous> (batch.js?jag=true&locale=en-US&sd_operational=true:1285:388)
at l (batch.js:6:2054)
at u (batch.js:6:946)
at l (batch.js:6:1959)
at u (batch.js:6:946)
at s (batch.js:6:2334)
at window.require (batch.js:9:200)
at batch.js?jag=true&locale=en-US&sd_operational=true:1291:19
at batch.js?jag=true&locale=en-US&sd_operational=true:1291:610
Which seems to be related to the underscore package which doesn't have the once function?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Andreas Gade Hjarnø Welcome to the community!
Could you please share details like is this the workflow Post function or automation rule?also, clear your browser cache and check once?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It is a workflow post function or I think it is called a screen function?. The browser cache clearing didn't change anything.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.