Details
-
Bug
-
Resolution: Fixed
-
Highest
-
72
-
Severity 2 - Major
-
26
-
Description
Summary
When a customer attempts to create, edit, or transition issues with JIRA, an error is displayed indicating an issue within the workflow. Subsequently the action cannot be carried out.
Environment
Cloud - v1000.350.1
Steps to Reproduce
- Attempt create a new issue
or - Attempt to transition an issue
or - Attempt to edit an existing issue
Expected Results
The issue should be created, transitioned to the next workflow step, or updated with the new information input in the edit window
Actual Results
The issue is not created, is not transitioned, is not updated. Instead the below error is displayed:
com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericEntityException: while inserting: [GenericEntity:ChangeGroup][issue,36800][author,xshi][created,2016-09-19 01:36:21.042][id,248500] (SQL Exception while executing the following:INSERT INTO public.changegroup (ID, issueid, AUTHOR, CREATED) VALUES (?, ?, ?, ?) (ERROR: duplicate key value violates unique constraint "pk_changegroup")) com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericEntityException: while inserting: [GenericEntity:ChangeGroup][issue,36800][author,xshi][created,2016-09-19 01:36:21.042][id,248500] (SQL Exception while executing the following:INSERT INTO public.changegroup (ID, issueid, AUTHOR, CREATED) VALUES (?, ?, ?, ?) (ERROR: duplicate key value violates unique constraint "pk_changegroup"))
Could not move to history step for #37504: root cause: while inserting: [GenericEntity:OSHistoryStep][owner,][caller,fthorp][dueDate,null][stepId,5][actionId,51][finishDate,2016-09-19 08:47:00.781][id,54640][startDate,2016-09-19 08:30:31.383][entryId,37504][status,null] (SQL Exception while executing the following:INSERT INTO public.OS_HISTORYSTEP (ID, ENTRY_ID, STEP_ID, ACTION_ID, OWNER, START_DATE, DUE_DATE, FINISH_DATE, STATUS, CALLER) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?) (ERROR: duplicate key value violates unique constraint "pk_os_historystep"))
In the place of "pk_os_historystep" you may also see:
- pk_historystep_prev
- pk_changeitem
- pk_changegroup
Workaround
JIRA Cloud Support is able to run an update against your JIRA database that will resolve the current issue.
Attachments
Issue Links
- is cloned by
-
JDEV-37446 Loading...
- relates to
-
- was cloned as
-