Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-92572

Disabling "Code" feature on team-managed project should hide "Development panel"

    • 1
    • 10
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Issue Summary

      Customer would like to disable "Code" feature on the team-managed (formerly next-gen) projects and that should hide the Development panel too and not just the Tab "Code"

      Steps to Reproduce

      1. Navigate to any team-managed (formerly next-gen) project.
      2. Disable "Code" feature on the project and check if the development panel is still visible.

      Expected Results

      Customer would want to have the development panel hidden when the code feature is disabled so that users are confused looking at the panel.

      Actual Results

      Code feature only disables the "Code" Tab under Project configuration.

      Workaround

      Disable the complete DVCS integration (which is not a feasible option).
      Or
      Alternatively:

      1. Create a new team-managed role based on the Member role.
      2. Disable the Access development tools permission.
      3. Associate all existing users in the old role with the new one.
      4. Ensure the project access is set to "Limited" (it doesn't work when access is set to "Open")

            [JRACLOUD-92572] Disabling "Code" feature on team-managed project should hide "Development panel"

            SET Analytics Bot made changes -
            Support reference count Original: 9 New: 10
            SET Analytics Bot made changes -
            UIS Original: 0 New: 1
            SET Analytics Bot made changes -
            UIS Original: 1 New: 0
            Chung Jeon made changes -
            Link New: This issue relates to JRACLOUD-92010 [ JRACLOUD-92010 ]
            SET Analytics Bot made changes -
            UIS Original: 0 New: 1
            Fye made changes -
            Description Original: h3. Issue Summary
            Customer would like to disable "Code" feature on the team-managed (formerly next-gen) projects and that should hide the Development panel too and not just the Tab "Code"

            h3. Steps to Reproduce
            # Navigate to any team-managed (formerly next-gen) project.
            # Disable "Code" feature on the project and check if the development panel is still visible.

            h3. Expected Results
            Customer would want to have the development panel hidden when the code feature is disabled so that users are confused looking at the panel.

            h3. Actual Results
            Code feature only disables the "Code" Tab under Project configuration.

            h3. Workaround
            Disable the complete DVCS integration (_which is not a feasible option_).
            Or
            Alternatively:
            # Create a new team-managed role based on the *Member* role.
            # Disable the *Access development tools* permission.
             !screenshot-1.png|thumbnail!
            # Associate all existing users in the old role with the new one.
            New: h3. Issue Summary

            Customer would like to disable "Code" feature on the team-managed (formerly next-gen) projects and that should hide the Development panel too and not just the Tab "Code"
            h3. Steps to Reproduce
             # Navigate to any team-managed (formerly next-gen) project.
             # Disable "Code" feature on the project and check if the development panel is still visible.

            h3. Expected Results

            Customer would want to have the development panel hidden when the code feature is disabled so that users are confused looking at the panel.
            h3. Actual Results

            Code feature only disables the "Code" Tab under Project configuration.
            h3. Workaround

            Disable the complete DVCS integration ({_}which is not a feasible option{_}).
            Or
            Alternatively:
             # Create a new team-managed role based on the *Member* role.
             # Disable the *Access development tools* permission.
            !screenshot-1.png|thumbnail!
             # Associate all existing users in the old role with the new one.
             # Ensure the project access is set to "Limited" (it doesn't work when access is set to "Open")
            SET Analytics Bot made changes -
            Support reference count Original: 8 New: 9
            SET Analytics Bot made changes -
            UIS Original: 1 New: 0
            SET Analytics Bot made changes -
            Support reference count Original: 7 New: 8
            SET Analytics Bot made changes -
            UIS Original: 0 New: 1

              Unassigned Unassigned
              a1303999a44a Kiran Talagana (Inactive)
              Votes:
              6 Vote for this issue
              Watchers:
              11 Start watching this issue

                Created:
                Updated: