Details
-
Bug
-
Resolution: Duplicate
-
Low
-
2.5.2 Professional, 2.5.2 Enterprise
-
2.05
-
Description
There is evidently a bug somewhere in JIRA, where the OS_CURRENTSTEP is at 5 ('Reopened') when the issue is at step 5 ('Resolved').
The effect of this is that the global 'Resolve' action is visible. Clicking this (resolving a resolved issue) fixes the problem.
In SQL, issues in this state can be determined with:
create index issue_wfid on jiraissue(WORKFLOW_ID);
create index currentstep_entry on OS_CURRENTSTEP(ENTRY_ID);
select j.pkey, j.issuestatus, c.STEP_ID from jiraissue j, OS_CURRENTSTEP c WHERE j.WORKFLOW_ID=c.ENTRY_ID and j.issuestatus=5 and c.STEP_ID=5;
Attachments
Issue Links
- relates to
-
JRASERVER-2709 (re)Assign is not always noticed in the dashboard
- Closed