-
Bug
-
Resolution: Low Engagement
-
Low (View bug fix roadmap)
-
None
-
6.4.5
-
6.04
-
1
-
Severity 3 - Minor
-
0
-
Summary
When a user imports his backup.xml from JIRA 5.X to a JIRA 6.4.5 instance, the users or groups allowed in the Transition Issue permission differs based on when he imported the data(during installation or after installation)
Steps to Reproduce
Ensure that the Transition Issue Permission in the 5.X instance has been modified before you backup the instance.
Test 1
- Download and Install JIRA 6.4.5
- When Installation is completed, import the backup into JIRA.
- Check your project with the modified transition issue permission.
Result
The permission matches what you had configured in JIRA 5.X
Test 2
- Download and Install JIRA 6.4.5
- While installing, when you get to the page that allows you import your data, select the option to import your backup.xml and import the data.
- Check your project with the modified transition issue permission.
Expected Result
The permission should match that of JIRA 5.X or at least match that of Test 1.
Actual Result
This permission would contain only 2 user/group:
- Single User
- Project Role(Developer)
This result can be seen in the image attached below:
- was cloned as
-
JPA-369 Failed to load
[JRASERVER-43863] Transition Permission Different Depending on when Data is restored in JIRA
| Resolution | New: Low Engagement [ 10300 ] | |
| Status | Original: Gathering Impact [ 12072 ] | New: Closed [ 6 ] |
| Labels | Original: affects-server warranty | New: affects-server cleanup-seos-fy25 warranty |
| UIS | Original: 1 | New: 0 |
| UIS | New: 1 |
| Minimum Version | New: 6.04 |
| Workflow | Original: JAC Bug Workflow v2 [ 2832299 ] | New: JAC Bug Workflow v3 [ 2931199 ] |
| Symptom Severity | Original: Minor [ 14432 ] | New: Severity 3 - Minor [ 15832 ] |
| Workflow | Original: JIRA Bug Workflow w Kanban v7 - Restricted [ 2553051 ] | New: JAC Bug Workflow v2 [ 2832299 ] |
| Status | Original: Verified [ 10005 ] | New: Gathering Impact [ 12072 ] |
| Workflow | Original: JIRA Bug Workflow w Kanban v6 - Restricted [ 1542999 ] | New: JIRA Bug Workflow w Kanban v7 - Restricted [ 2553051 ] |
Hi,
At Atlassian, our goal is to ensure we’re providing the best experience for our customers. With our new Data Center strategy, Atlassian's focus is on security, compliance, and performance and is a key driver in prioritizing bugs. Closing the bugs that do not fall into those categories will allow us to focus on the ones in the most current versions of our products.
This bug is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments; this inactivity suggests a low impact.
Please note the comments on this thread are not being monitored.
You can read more about our bug fix policy here and how we prioritize bugs.
To learn more about our recent investments in Jira Data Center, please check our public roadmap and dashboards containing recently resolved issues, current work, and future plans.
Kind regards,
Jira Data Center