-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
9.5.1
-
None
-
9.05
-
12
-
Severity 3 - Minor
-
1
-
Issue Summary
RAPID_VIEW_ID value within the AO_60DB71_SPRINT set null after migrating Jira projects from one Jira instance to another using Jira's Project Import feature (using XML Backup).
The null value of RAPID_VIEW_ID results in the missing attribute "originBoardID" in the response of the REST call GET <jira_base>/rest/agile/1.0/board/<BoardID>/sprint
Steps to Reproduce
On the source Jira:
- Create a project
- Create Board ( Assume board ID is 1)
- Create one or more sprint
- Query the "AO_60DB71_SPRINT" table and verify RAPID_VIEW_ID is not null
SELECT * from "AO_60DB71_SPRINT"
Beware that the query syntax might be different for different databases. The sample query above is tested with Postres 12
- Run the REST call GET <jira_base>/rest/agile/1.0/board/1/sprint (BoardID replaced with the actual board ID which is 1) and verify origionBoardID exists in the response
{ "maxResults": 50, "startAt": 0, "isLast": true, "values": [ { "id": 4, "self": "http://10.227.139.246:8080/rest/agile/1.0/sprint/4", "state": "closed", "name": "Sample Sprint 1", "startDate": "2023-01-02T02:22:58.295Z", "endDate": "2023-01-16T02:22:58.295Z", "completeDate": "2023-01-16T01:02:58.295Z", "activatedDate": "2023-01-02T02:22:58.295Z", "originBoardId": 2, "synced": false, "autoStartStop": false }, { "id": 3, "self": "http://10.227.139.246:8080/rest/agile/1.0/sprint/3", "state": "active", "name": "Sample Sprint 2", "startDate": "2023-01-16T03:32:56.835Z", "endDate": "2023-01-30T03:52:56.835Z", "activatedDate": "2023-01-16T03:32:56.835Z", "originBoardId": 2, "synced": false, "autoStartStop": false } ] }
- Take an XML backup
On the target Jira; - Import project using the Project Import tool
- Query the "AO_60DB71_SPRINT" table and verify RAPID_VIEW_ID is Null for the newly added rows.
SELECT * from "AO_60DB71_SPRINT"
- Run the REST call GET <jira_base>/rest/agile/1.0/board/<BoardID>/sprint (BoardID replaced with the actual board ID which is 1) and verify origionBoardID NOT exists in the response
{ "maxResults": 50, "startAt": 0, "isLast": true, "values": [ { "id": 6, "self": "http://10.227.139.246:8080/rest/agile/1.0/sprint/6", "state": "closed", "name": "Sample Sprint 1", "startDate": "2023-01-02T02:22:58.295Z", "endDate": "2023-01-16T02:22:58.295Z", "completeDate": "2023-01-16T01:02:58.295Z", "activatedDate": "2023-01-02T02:22:58.295Z", "synced": false, "autoStartStop": false }, { "id": 5, "self": "http://10.227.139.246:8080/rest/agile/1.0/sprint/5", "state": "active", "name": "Sample Sprint 2", "startDate": "2023-01-16T03:32:56.835Z", "endDate": "2023-01-30T03:52:56.835Z", "activatedDate": "2023-01-16T03:32:56.835Z", "synced": false, "autoStartStop": false } ] }
Expected Results
- origionBoardID attribute should exist within the response for the REST call <jira_base>/rest/agile/1.0/board/<BoardID>/sprint
- RAPID_VIEW_ID value for the newly added sprints within the table AO_60DB71_SPRINT shouldn't be null
Actual Results
- origionBoardID attribute is missing within the response of the REST call <jira_base>/rest/agile/1.0/board/<BoardID>/sprint
- RAPID_VIEW_ID value for the newly added sprints within the AO_60DB71_SPRINT table is Null
Workaround
- Update the database manually and set values for the RAPID_VIEW_ID value within the AO_60DB71_SPRINT
- Restart Jira after DB updates
-
-
- Tested with 8.21 and 9.5.1
-