-
Bug
-
Resolution: Low Engagement
-
Low
-
None
-
3.6.1, 3.8.3, 4.5.2, 4.7.0
-
1
-
Severity 3 - Minor
-
Issue description
When the Satisfaction field is added to the Issue Edit Screen, the Satisfaction panel disappears whenever an issue is deleted
Steps to reproduce
- Open a Service Desk issue that already has a Customer Satisfaction rating
- Click on "Edit", don't change anything in the Edit form, then click on "Update".
- Verify that the Customer Satisfaction panel is still here:
- Click again on "Edit", and this time, then click on "Configure Fields" > "Where is my field?" and look for "Satisfaction"
- Click on the link to the screen used by the Issue Edit Form and add the field "Satisfaction" to the screen:
- Go back to the issue and click on "Update" (without updating any field in the ticket)
Actual Result
The "Customer Satisfaction" panel disappears:
Expected Result
The "Customer Satisfaction" panel should not disappear.
Suggestions for the resolution of this bug
2 options:
- Either prevent the admin user from adding the "Satisfaction screen", since this field is not editable anyway.
- Or prevent the "Update" button from clearing the "Customer Satisfaction" panel
Workaround
Don't include the "Satisfaction" field from the Edit screen.
- links to
- mentioned in
-
Page Failed to load
[JSDSERVER-5614] When the Satisfaction field is added to the Issue Edit Screen, the Satisfaction panel disappears whenever an issue is deleted
| Resolution | New: Low Engagement [ 10300 ] | |
| Status | Original: Gathering Impact [ 12072 ] | New: Closed [ 6 ] |
| Labels | Original: non-warranty ril | New: cleanup-seos-fy25 non-warranty ril |
| Labels | Original: non-warranty | New: non-warranty ril |
| Remote Link | New: This issue links to "Internal ticket (Web Link)" [ 955050 ] |
| Labels | New: non-warranty |
| Status | Original: Needs Triage [ 10030 ] | New: Gathering Impact [ 12072 ] |
| Affects Version/s | New: 4.5.2 [ 90400 ] | |
| Affects Version/s | New: 4.7.0 [ 90597 ] |
| Remote Link | New: This issue links to "Page (Confluence)" [ 461318 ] |
| Workflow | Original: JSD Bug Workflow v5 - TEMP [ 2505117 ] | New: JAC Bug Workflow v3 [ 3126273 ] |
| Status | Original: Untriaged [ 11672 ] | New: Needs Triage [ 10030 ] |
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.
We appreciate your time in submitting bugs to our product team and encourage you to continue doing so. Many features and functions in our products come from valued customers such as yourself. You can read more about our bug fix policy here and how we prioritize bugs.
To learn more about our recent investments in Jira Service Management Data Center, please check our public roadmap and dashboards containing recently resolved issues, current work, and future plans.
Kind regards,
Jira Service Management Data Center