-
Bug
-
Resolution: Cannot Reproduce
-
Low
-
None
-
6.1
-
6.01
-
Problem
See the table below:
ghs-9961=# select * from changeitem where groupid in (select id from changegroup where issueid in (69951)) and field in ('status', 'Project', 'Workflow')order by ID; id | groupid | fieldtype | field | oldvalue | oldstring | newvalue | newstring ---------+---------+-----------+----------+----------+-----------------------------+----------+------------------------------------- 125793 | 103861 | jira | status | 1 | Open | 10039 | Minor Platform Backlog 457403 | 306252 | jira | Project | 10202 | Change Requests | 10341 | Feature Request 457405 | 306252 | jira | Workflow | 75817 | xxxxxx xx xxxxxxxx | 148100 | Feature Request Workflow 1777902 | 1168181 | jira | Workflow | 148100 | Feature Request Workflow | 336599 | Feature Request Workflow II 2248090 | 1488772 | jira | Workflow | 336599 | Feature Request Workflow II | 409602 | Copy of Feature Request Workflow II 2248091 | 1488772 | jira | status | 10060 | Backlog | 10059 | Roadmap Control Board
When the issue is migrated to the new project and workflow, the issue didn't transition correctly from the previous status "Minor Platform Backlog" to "Backlog".
Expected Behavior
When the issue migrated to new project and workflow, it is expected to have transition from the previous status (ie. Minor Platform Backlog) to the new status (ie. Backlog).
Problem
The missing transition breaks some chart reporting in JIRA Agile which highly depends on the changeitem (issue history).
So far support unable to reproduce this behavior. This indicates this behavior is triggered by very specific and rare condition. This bug is to keep track if there is more users affected by this problem and found the explicit way to reproduce this.
- is related to
-
-
- Gathering Impact
-