Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-59078

Issue Navigator screen does not respect JIRA's "Inline Edit" System setting

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Low Low
    • None
    • 7.0.0
    • Issue - Fields

      Cloned from JSD-2419

      This was cloned from JSD issue, as during our investigations we found the following:

      • JIRA Issue View honours the Inline Edit Setting as expected
      • JIRA Issue Navigator and JIRA Software boards (as well as JIRA Service Desk queues) do not honour this setting.
      • It appears as though an underlying fix to the Issue Navigator is required that should filter through to JIRA Software and JIRA Service Desk
      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.

        1. system_settings.png
          system_settings.png
          96 kB
        2. Inline edit 2.png
          Inline edit 2.png
          230 kB
        3. Inline edit 1.png
          Inline edit 1.png
          220 kB

              Unassigned Unassigned
              mmcmahon Matthew McMahon (Inactive)
              Votes:
              4 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: