Details
-
Suggestion
-
Resolution: Unresolved
-
10
-
16
-
Description
Issue Summary
This is reproducible on Data Center: yes
Steps to Reproduce
In cloud:
- Create a scrum project PROJA
- Create 3 sprints in PROJA containing some sample issues
- Now we have at least 3 sprints in the cloud site
In server:
- Create a scrum project PROJB
- Create a sprint in PROJB containing some sample issues
- Create a filter "Test filter projb" that includes the project PROJB and containing the new sprint
- The Advanced JQL should look something like "project = PROJB AND Sprint = 3"
- Go to the board for PROJB and change the filter to the new filter you created "Test filter projb"
- Migrate PROJB to the cloud site using JCMA
Expected Results
- The filter "Test filter projb" should include the same Sprint in the cloud as in the server (from PROJB).
Actual Results
- Since the Sprint IDs are not updated in the filter JQL during the migration, the filter "Test filter projb" isn't pointing to the same sprint as in the server.
- The filter is pointing to the sprint that has the same ID in the cloud site (such as a sprint from PROJA) and not the sprint from PROJB.
- This can also result in broken filters when the sprint ID is not valid in the cloud site.
No errors are thrown in the log file.
Workaround
A manual workaround is to edit the filter in the cloud site to point to the actual sprint.
If the manual workaround isn't feasible please engage support.
Attachments
Issue Links
- is related to
-
MIG-907 JQL board filter using project id doesn’t bring expected results after migrating via JCMA
- Gathering Interest
-
MIG-180 JCMA should validate JQL filters for validity pre-migration
- Not Being Considered
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...