Remove previous Jira history from the content of incoming emails (which are replies to Jira notifications)

XMLWordPrintable

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

      Please parse reply emails and remove Jira history content. Something like: if the email subject contains a Jira project key
      then look at the content and delete anything below the first email header that contains that key.

      We use Jira to track field issues and provide field support.
      1. Field staffer creates a Jira issue (either directly or via email).
      2. Support staff in head office make a comment in Jira.
      3. Field staffer receives a notification email containing the comment.
      5. Field staffer then typically replies "with history".
      6. Their reply with all of its history is added as one Jira comment, but that same history is already tracked (in a much nicer way) through individual Jira comments. This adds accumulated redundant information for each emailed reply "with history". After only a few replies such a Jira issue is very difficult to read, to the point of being counter-productive.

      Field staff prefer email over Jira web access because they travel alot and don't always have access to the internet. But they do have access to a local replica of their email database on their laptops. This means they can work offline and respond to our questions straight after leaving a customer site (on a plane or train) while vital new information is fresh.

      We have asked field staff to reply "without history" but this never works. They want to see what they're replying to and they always want to cc other staff in regional offices who have more access to internet and can "watch" issues.

            Assignee:
            Unassigned
            Reporter:
            Allan Novakovich
            Votes:
            2 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: