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

Helpdesk features

    XMLWordPrintable

Details

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

    Description

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

      (from customer email):

      We had been using RT/WebRT, but found that after >400 tickets, the
      system began to slow to a crawl (it doesn't appear that JIRA suffers from this problem, though). We are a small company with 2 people (also software engineers) doing the bulk of the support work. So when I think of a support tracker for our use, I imagine it having, as you say, a pretty simple feature set:

      • Ability to receive external e-mail, create a ticket, and have
        certain comments (correspondence) sent back to the originator/
        requestee.
      • Status per ticket
      • Owner per ticket
      • Attachment handling is nice also.

      We don't really deal with any notions of priority and/or escalation of
      support tickets here, as there is usually only a small amount of traffic. I should add that I would like these support tickets to be
      'interchangable' with normal issues in JIRA. They might be created in a default project, but could be moved to other projects and still maintain the requestee, etc.

      In the future I can imagine us exposing JIRA to our customers and
      importing a customer username/password database already in use, but for now we are mostly interested in e-mail support management.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              scott@atlassian.com Scott Farquhar
              Votes:
              17 Vote for this issue
              Watchers:
              16 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: