Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-2326

Advanced email support


    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • Email notifications
    • None
    • 2
    • We collect Jira 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 Server. Using JIRA Cloud? See the corresponding suggestion.

      This is a 'meta-issue' for linking all issues related to advanced email support. That is, towards being able to use email as a primary JIRA interface – ideally, not even be aware that JIRA is involved.

      The biggest use-case I have is public opensource projects. All communication happens over email, and there is very little distinction between an email and an issue, neither conceptually nor physically (the tracker is configured to send emails for new issues/comments). Frequently, long conversations are held via comments in an issue [1]

      For established projects, a significant proportion (~40%) of non-cvs emails are generated by the issue tracker. It would be a massive timesaver if developers didn't need to run off to a web interface to comment on issues.

      JIRA has some rudimentary support for this (CreateOrCommentHandler), but JIRA-generated emails:

      • do not support threading (JRA-1113)
      • are IMHO pretty ugly and not easy to scan quickly compared to Bugzilla's. (JRA-3719)
      • do not customize the From: address to indicate who the commenter is. (JRA-2315)

      So I think getting decent email support would be a fantastic way of capturing the lucrative open-source market. More than any other feature, it would leapfrog JIRA over its competitors.

      If JIRA's email support was enhanced sufficiently, it could also be used as a support system backend, tracking support requests, not least here at Atlassian. This is a whole new market, probably justifying a new product stream, but I think the enhancements mentioned above would give us an 80:20 solution.


      [1] For example, see some of Mozilla's longer threads, like http://bugzilla.mozilla.org/show_bug.cgi?id=97284 .

            Unassigned Unassigned
            7ee5c68a815f Jeff Turner
            22 Vote for this issue
            13 Start watching this issue