Forums

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

EDIT, ASSIGN and changing status in workflow buttons don't work (intermittenly) - how to fix?

Alastair Fife
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!
July 11, 2018

When I load an issue and try to click on the EDIT or ASSIGN buttons (or try and change the status in the workflow, by clicking on the IN PROGRESS button) the screen darkens, I see the loading wheel spinning, but nothing happens. I have to escape to return to the issue screen.  Occasionally, the problem doesn't manifest and I can EDIT or ASSIGN or change workflow without this problem, but there appears to be no logic to when this happens, and it is maybe a 1 in 20 occurence (that it works).  Keyboard shortcuts result in the same problem.

 

 

I know there are other ways to e.g. edit parts of the issue (by clicking on the actual field I want to change) but this problem is a real pain, especially for the workflow status change.

I'm using the simplified software dev workflow, and only have 30 tickets in the DB so don't have a complicated or large volume JIRA project as we-re just setting it up.  I'm also an administrator/superuser of the project so shouldn't have permission problems.

 

Thoughts, solutions, appreciated!

 

Tech note:

JIRA version 7.5.1

Viewing via Chrome 67.0.3396.99 64-bit on a Windows 10 (v1803) laptop.

1 answer

0 votes
Deleted user
July 11, 2018

Hi @Alastair Fife,

Have you contacted Atlassian Support? My suggestion would be to provide them with a performance log recorded via Chrome's Dev tools as this may help speed up the process to find the source of the intermittent issue. 

Hope this helps

Alastair Fife
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!
July 11, 2018

Hi Danny, thanks for the quick response.  The support request is in progress but no response yet.  If I get it solved by them, I will post here. 

I just thought the community might have seen something like this before and have a solution.  

Deleted user
July 11, 2018

I wish I could offer one. I have had a similar issue with a previous instance, the Atlassian Support team were able to provide a solution after diagnosing the source of the issue.

Hope your issue gets sorted 

Suggest an answer

Log in or Sign up to answer