Jira fails to create isses and changes state of isses.

[Thành Vũ]

Hi, I have done migration of Jira application (8.20.1) from cloud to server (8.16.1) + Postgres 9.6 , after doing data backup from Cloud and restore to Server, I get my project, but the big problem is that I can't change the status of issues, or create 1 new issue, maybe I missed some configuration. Please help me or ask a question below, thanks.

[Andy Heinzer · Accepted solution]

Hi @Thành Vũ 

If I understand correctly, you have recently migrated Jira from Cloud to server.  However since that time you are unable to create new issues or transition issues. 

The first thing that comes to my mind in this case is the permissions of the user that is logged into Jira.  If this user does not have the needed permissions it would explain those to behaviors.  You can use something such as a the Jira Admin Helper, specifically the permission checker, to see if your account is expected to be able to create/transition.  And if it is not able to due to permissions, the links in that tool can help you to easily correct this.

If that isn't he problem, I'd be interested to learn more here.  What happens when you try to create a new issue?  If Jira appears to let you complete the create process but does not create the issue, then I'd be interested to take a closer look at the $JIRAHOME/log/atlassian-jira.log at the time of this issue creation attempt.  That log file should then be able to tell us if there is something like a SQL exception that is preventing the issue creation here.

[Thành Vũ]

Thank you for your reply, it means a lot to me.

This is exactly what appears when I create a new task :

postgres | 2021-11-18 02:01:12.608 UTC [39] ERROR: duplicate key value violates unique constraint "pk_customfieldvalue"
postgres | 2021-11-18 02:01:12.608 UTC [39] DETAIL: Key (id)=(13400) already exists.
postgres | 2021-11-18 02:01:12.608 UTC [39] STATEMENT: INSERT INTO public.customfieldvalue (ID, ISSUE, CUSTOMFIELD, UPDATED, PARENTKEY, STRINGVALUE, NUMBERVALUE, TEXTVALUE, DATEVALUE, VALUETYPE) VALUES ($1, $2, $3, $4, $5, $6, $7, $8, $9, $10)
postgres | 2021-11-18 02:01:29.012 UTC [39] ERROR: function aurora_version() does not exist at character 8
postgres | 2021-11-18 02:01:29.012 UTC [39] HINT: No function matches the given name and argument types. You might need to add explicit type casts.

and I don't have much experience in data processing.

[Thành Vũ]

Maybe I found the solution to my problem after reading a similar error here:

https://jira.atlassian.com/browse/JSDSERVER-6539?workflowName=JAC+Bug+Workflow+v3&stepId=2

Thank you,  @Andy Heinzer.