Jira slow or unresponsive when Assignee field is on edit screen

[David Letts]

Hi,

We're having issues with our Jira instance where it is either taking a long time to open the edit screen, or eventually timing out without opening the screen at all.

We've tracked it down to having the Assignee field included on the edit screen - if it's included on that screen it is either slow or times out, if it's removed from the edit screen then it opens almost instantly.

We've tried turning on the SQL logging and the below query seems to be taking a long time to run:

SELECT CG.ID, CG.issueid, CG.AUTHOR, CG.CREATED, CI.ID, CI.groupid, CI.FIELDTYPE, CI.FIELD, CI.OLDVALUE, CI.OLDSTRING, CI.NEWVALUE, CI.NEWSTRING FROM JIRASchema.changegroup CG INNER JOIN JIRASchema.changeitem CI ON CG.ID = CI.groupid WHERE CG.issueid='XXXXX' AND CI.FIELD='assignee' ORDER BY CG.CREATED ASC, CI.ID ASC

If we run this query directly against the database it runs quickly with no issues. This has only just started happening with Jira no changes that we're aware of.

Has anyone seen an issue like this before or know what we can try to resolve this issue?

[David Letts]

Hi Will, Yes we managed to resolve it. In our case adding the indexes mentioned in this link instantly fixed it.

https://jira.atlassian.com/browse/JRASERVER-63002

CREATE UNIQUE INDEX JIRADBUSER.CHANGEGROUP_SCX1
 ON JIRADBUSER.CHANGEGROUP
(ISSUEID, ID)
TABLESPACE JIRA_DATA;

CREATE INDEX JIRADBUSER.CHANGEITEM_SCX1
 ON JIRADBUSER.CHANGEITEM
 (GROUPID, FIELD)
TABLESPACE JIRA_DATA;

[Will C]

Hey David, did you ever get an answer or fix for this?