• Icon: Suggestion Suggestion
    • Resolution: Duplicate
    • None
    • None
    • None
    • 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.

      Currently, only issues that are raised via Service Desk are viewable when a user accesses the 'My Requests' section.

      It would be more helpful (and also allows Service Desk to be a one-stop centre for users) if they can view all the issues raised by them regardless of origin (from JIRA, from email, etc) in the 'My Requests' section.

          Form Name

            [JSDSERVER-129] Allow all requests to be seen by the user

            shihab added a comment -

            Thanks for raising this feature request.

            The Customer Portal in JIRA Service Desk displays Request Types to users. A Request Type is essentially an Issue Type template - you can rename and hide fields, preset values, etc. As an admin, you have the choice to:

            • define multiple request types that back off the one issue type (eg. "Printer Request" and "Computer Request" might both be "Hardware Issues")
            • have issue types that have no request types associated with it (eg. you may not want end users to create "Internal Issues" via the customer portal).

            This is why it's not possible to map every single JIRA issue to a request type. Service Desk will automatically link request types to issues that are created via the Customer Portal, but for issues created via JIRA or via JIRA email handlers, they will not be linked to a request type.

            We have two open feature requests that can address the underlying problems you describe:

            • JSD-55: allow you to set the request type for existing issues, so that they show up in the Customer Portal. This will allow you to specify what request type you want to use to in order to display the issue, eg. if you have "Hardware" issues, you will need to decide whether they are "Computer Requests" or "Printer Requests" and set the field accordingly.
            • JSD-38: allow you to define email handlers that link to request types. This will give you the ability to link email addresses to specific request types so all emails that come in are automatically linked to a defined request type.

            shihab added a comment - Thanks for raising this feature request. The Customer Portal in JIRA Service Desk displays Request Types to users. A Request Type is essentially an Issue Type template - you can rename and hide fields, preset values, etc. As an admin, you have the choice to: define multiple request types that back off the one issue type (eg. "Printer Request" and "Computer Request" might both be "Hardware Issues") have issue types that have no request types associated with it (eg. you may not want end users to create "Internal Issues" via the customer portal). This is why it's not possible to map every single JIRA issue to a request type. Service Desk will automatically link request types to issues that are created via the Customer Portal, but for issues created via JIRA or via JIRA email handlers, they will not be linked to a request type. We have two open feature requests that can address the underlying problems you describe: JSD-55 : allow you to set the request type for existing issues, so that they show up in the Customer Portal. This will allow you to specify what request type you want to use to in order to display the issue, eg. if you have "Hardware" issues, you will need to decide whether they are "Computer Requests" or "Printer Requests" and set the field accordingly. JSD-38 : allow you to define email handlers that link to request types. This will give you the ability to link email addresses to specific request types so all emails that come in are automatically linked to a defined request type.

            I think this duplicates JSD-55.

            UoS Web Team People added a comment - I think this duplicates JSD-55 .

              Unassigned Unassigned
              jtye Joe Wai Tye (Inactive)
              Votes:
              5 Vote for this issue
              Watchers:
              13 Start watching this issue

                Created:
                Updated:
                Resolved: