Uploaded image for project: 'Jira Service Management Cloud'
  1. Jira Service Management Cloud
  2. JSDCLOUD-9226

In the new issue view it's not possible to edit the issue layout of subtasks to remove the request type

      Issue Summary

      For Service Desk projects with the new issue view, you have no way to control sub-task screens. Service Desk does that configuration under Request Types and sub-tasks cannot have a Request Type.

      It's not possible to use the "Configure" feature to edit the issue layout because the Subtask doesn't have a Request Type.

      The same applies to issue types that don't have a request type associated with.

      Steps to Reproduce

      1. In a Service Desk project create a subtask;
      2. Try to edit the issue layout in order to remove the request type;

      Expected Results

      It's possible to edit the issue layout and remove the request type since it's not used.

      Actual Results

      It's not possible to edit the issue layout because the issue type doesn't have a request type.

      Workaround

      Currently, there is no known workaround for this behavior. A workaround will be added here when available.

            [JSDCLOUD-9226] In the new issue view it's not possible to edit the issue layout of subtasks to remove the request type

            Greg D added a comment -

            Why would this be intended functionality that you cannot edit the view of a subtask screen at all?  Can we get it on the https://jira.atlassian.com/browse/JRACLOUD-70555 at least then?

            Greg D added a comment - Why would this be intended functionality that you cannot edit the view of a subtask screen at all?  Can we get it on the https://jira.atlassian.com/browse/JRACLOUD-70555  at least then?

            Emma Young added a comment -

            We have closed off this bug ticket in favour of creating a suggestion ticket, as at this time this is intended functionality and not a bug.

            https://jira.atlassian.com/browse/JSDCLOUD-9230

            Emma Young added a comment - We have closed off this bug ticket in favour of creating a suggestion ticket, as at this time this is intended functionality and not a bug. https://jira.atlassian.com/browse/JSDCLOUD-9230

            Greg D added a comment -

            Not sure if it would work since the infrastructure is completely different for Service Desk projects, but if you could somehow allow us to get solely to the issue layout configuration by directly navigating to a screen id,  I think that would be great (like you do for issue layouts in other project types).

            e.g. atlassian.net/plugins/servlet/project-config/<servicedeskprojectkey>/issuelayout?screenId=10004

             

            That way you drive most people to the request type section to control both their request fields and issue layout (current state), but for sub-tasks and advanced use-cases of issues without request types that are in the project, we can actually control the screens.  So for the simple users you don't duplicate issue layout in the project settings UI, but we have a way to get there.  Alternatively, if you do want it in the UI, you can have something called "Empty Request Type Issue Layout" .... that could be used to set the default views that align with classic screens before a request type is added.  And then it would be nice if the Request Type box could be hidden (but if it has to stay with Reporter and Channel, that works).

            Greg D added a comment - Not sure if it would work since the infrastructure is completely different for Service Desk projects, but if you could somehow allow us to get solely to the issue layout configuration by directly navigating to a screen id,  I think that would be great (like you do for issue layouts in other project types). e.g. atlassian.net/plugins/servlet/project-config/<servicedeskprojectkey>/issuelayout?screenId=10004   That way you drive most people to the request type section to control both their request fields and issue layout (current state), but for sub-tasks and advanced use-cases of issues without request types that are in the project, we can actually control the screens.  So for the simple users you don't duplicate issue layout in the project settings UI, but we have a way to get there.  Alternatively, if you do want it in the UI, you can have something called "Empty Request Type Issue Layout" .... that could be used to set the default views that align with classic screens before a request type is added.  And then it would be nice if the Request Type box could be hidden (but if it has to stay with Reporter and Channel, that works).

              Unassigned Unassigned
              0d59956c4fe8 Pedro Henrique Fernandes
              Affected customers:
              1 This affects my team
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: