-
Bug
-
Resolution: Duplicate
-
Low
-
None
-
2.5.6
Scenario
1. Disable inline editing in JIRA's System Settings.
2. In the Service Desk menu, click on a service desk, so you get to see the Queues screen.
3. Click on an issue.
Expected behaviour
The issue should not be editable inline because this is disabled in JIRA's system settings.
Actual behaviour
The fields of the issue are editable inline.
E.g. the description field:
E.g. the priority field:
There are several reasons why we want to disable inline editing:
- We want to limit the number of notifications customers receive. In an edit dialog, users are more likely to update all fields at once.
- Some plugins can add custom fields that depend on each other (E.g. Kepler Database Custom Field supports child fields). These work well in an edit dialog, but not so well when editable inline.
- is caused by
-
-
- Closed
-
- relates to
-
JSDSERVER-1211 Customer Request Type not visible on edit and create screens
- Closed
-
DESK-4558 Failed to load
-
JSDS-564
You do not have permission to view this issue
- was cloned as
-
-
- Closed
-
-
DESK-4438 Loading...
-
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSDSERVER-2419] Service Desk "Queues" screen does not respect JIRA's "Inline Edit" System setting
I have created JRA-59078 based off this issue, as our investigations have found that it is JIRA problem with the Issue Navigator component.
Once that is rectified, or more information is available, we can update this issue.
Regards
Matt
JIRA Service Desk developer
Closed as a duplicate of
JRA-59259This will be resolved once that issue is fixed