• 51
    • 7
    • We collect Jira Service Desk feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding suggestion.

      Problem Definition

      Some customers who are both an Approver and a Service Desk Agent would like to be able to assign the Service Desk Request when they Approve/Deny the Request in one step
      It appears that screens can be added to the transition, however they do not appear when the Approve/Deny buttons are used.

      Suggested Solution

      Allow for Screens to be used on the Approve/Deny Transitions added by Service Desk

      Workaround

      Current process is 2 Steps (Tested this workaround but it did not work):

      • Approver clicks Approve/Deny (either in JIRA or Portal views)
      • Agent/Collaborator clicks assign to assign Request to an Agent

          Form Name

            [JSDSERVER-3980] Use Screens on Approve/Deny Service Desk Transitions

            Dear Customers, 

            After comparing this Feature request request against the known bug report JSDSERVER-4789 we realized that both are addressing the same scenario and we are considering this a bug rather than a feature at this point.

            Since we consider JSDSERVER-4789 the main point of entry for this scenario, we will be closing this request now and will ask you to cast your votes and watch the bug request so we can measure the impact and interest more accurately. If you believe that this has been done in error please raise a Support request at support.atlassian.com and we will review the requests again to address it.

            Regards,
            Earl McCutcheon | Atlassian Community Support Team

            Earl McCutcheon added a comment - Dear Customers,   After comparing this Feature request request against the known bug report JSDSERVER-4789 we realized that both are addressing the same scenario and we are considering this a bug rather than a feature at this point. Since we consider JSDSERVER-4789 the main point of entry for this scenario, we will be closing this request now and will ask you to cast your votes and watch the bug request so we can measure the impact and interest more accurately. If you believe that this has been done in error please raise a Support request at   support.atlassian.com   and we will review the requests again to address it. Regards, Earl McCutcheon | Atlassian Community Support Team

              Unassigned Unassigned
              scranford Shawn C
              Votes:
              58 Vote for this issue
              Watchers:
              45 Start watching this issue

                Created:
                Updated:
                Resolved: