• 0
    • 8
    • 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.

      Support processing Old Email that is not created as a Request yet

      The current behaviour for JIRA ServiceDesk Email Settings(Mail Handler) is to "Read/Pull" an "Unread" messages that were inside the Mail Box. After it is being pulled it will be set as Read and the emails is converted as Request in the JIRA ServiceDesk Project. As mentioned in the documentation:

      After the email channel is set up, JIRA Service Desk will take note of when it connected to the email account for the first time. Any new messages sent to your inbox after that time will be pulled in as new requests or comments. Customers will receive email notifications about the details of their requests. For information about notifications, see Configuring JIRA Service Desk notifications. Messages that already exist in your email account are not processed. 

      But, there is still possibility that one of the new email is already "Read" before JIRA ServiceDesk pull it making it is not being created as a Request. Hence, just like the Standard JIRA Mail Handler where it will scan the Mail Box as it is configured and it will created any emails as JIRA Issue if the issue is not exist yet, it would be great that JIRA ServiceDesk Email Settings(Mail Handler) have the same features like Standard JIRA Mail Handler.

      Additional request:

      Make a way so that when a user is adding a Service Desk Channel, they are able to specify their own PULL_FROM_DATE rather than by default use the date that the Channel is created.

          Form Name

            [JSDSERVER-1509] Support processing Old Email that is not created as a Request yet

            Alex Cooksey made changes -
            Resolution Original: Won't Do [ 10000 ] New: Low Engagement [ 10300 ]
            Status Original: Closed [ 6 ] New: Closed [ 6 ]
            Charlie Marriott made changes -
            Resolution New: Won't Do [ 10000 ]
            Status Original: Gathering Interest [ 11772 ] New: Closed [ 6 ]
            SET Analytics Bot made changes -
            UIS Original: 1 New: 0
            SET Analytics Bot made changes -
            UIS New: 1
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3012752 ] New: JAC Suggestion Workflow 3 [ 3650175 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2664984 ] New: JAC Suggestion Workflow [ 3012752 ]
            SET Analytics Bot made changes -
            Support reference count Original: 7 New: 8
            SET Analytics Bot made changes -
            Support reference count Original: 8 New: 7
            SET Analytics Bot made changes -
            Support reference count New: 8
            Owen made changes -
            Workflow Original: JSD Suggestion Workflow - TEMP [ 2321498 ] New: Confluence Workflow - Public Facing v4 [ 2664984 ]
            Status Original: Open [ 1 ] New: Gathering Interest [ 11772 ]

              Unassigned Unassigned
              jrahmadiputra Julian (Inactive)
              Votes:
              8 Vote for this issue
              Watchers:
              10 Start watching this issue

                Created:
                Updated:
                Resolved: