Top Menu

Jump to content
Home
    • Projects
    • Work packages
    • News
    • Getting started
    • Introduction video
      Welcome to OpenProject Community
      Get a quick overview of project management and team collaboration with OpenProject. You can restart this video from the help menu.

    • Help and support
    • User guides
    • Videos
    • Shortcuts
    • Community forum
    • Professional support

    • Additional resources
    • Data privacy and security policy
    • Digital accessibility (DE)
    • OpenProject website
    • Security alerts / Newsletter
    • OpenProject blog
    • Release notes
    • Report a bug
    • Development roadmap
    • Add and edit translations
    • API documentation
  • Sign in
      Forgot your password?
      Create a new account

      or sign in with your existing account

      Google

Side Menu

  • Overview
  • Activity
  • Roadmap
  • Work packages
  • Calendars
  • Team planners
  • Boards
  • Forums
  • Wiki
    • Table of contents
      • Expanded. Click to collapseCollapsed. Click to showDeveloper
        • Hierarchy leafAccessibility Checklist
        • Hierarchy leafCode Review Guidelines
        • Expanded. Click to collapseCollapsed. Click to showContribution
          • Hierarchy leafGit Workflow
          • Hierarchy leafTranslations
        • Expanded. Click to collapseCollapsed. Click to showDeveloping Plugins
          • Hierarchy leafDeveloping an OmniAuth Authentication Plugin
        • Hierarchy leafRelease Process
        • Hierarchy leafReport a bug
        • Hierarchy leafSecurity
        • Hierarchy leafSetting up an OpenLDAP server for testing
        • Hierarchy leafTheme Features
      • Hierarchy leafDownload
      • Expanded. Click to collapseCollapsed. Click to showFeature tour
        • Hierarchy leafRelease Notes OpenProject 30
        • Expanded. Click to collapseCollapsed. Click to showRelease Notes OpenProject 30 - Overview
          • Hierarchy leafGlossary
          • Hierarchy leafRelease Notes - Accessibility
          • Hierarchy leafRelease Notes - Accessibility changes
          • Hierarchy leafRelease Notes - Add work package queries as menu items to sidebar
          • Hierarchy leafRelease Notes - Copy projects based on Templates
          • Hierarchy leafRelease Notes - Design changes
          • Hierarchy leafRelease Notes - Fixed Bugs
          • Hierarchy leafRelease Notes - Keyboard Shortcuts
          • Hierarchy leafRelease Notes - Project settings
          • Hierarchy leafRelease Notes - Ruby&Rails Update
          • Hierarchy leafRelease Notes - Security
          • Hierarchy leafRelease Notes - Timelines
          • Hierarchy leafRelease Notes - Work packages
      • Hierarchy leafHowto create animated gifs
      • Hierarchy leafMigration Squashing
      • Hierarchy leafMod security
      • Hierarchy leafNew work package page
      • Hierarchy leafOP3 to OP4 Debian upgrade
      • Hierarchy leafOP4 Ubuntu1404 Stable with MySQL in production
      • Hierarchy leafOpenProject 40 Development Setup
      • Expanded. Click to collapseCollapsed. Click to showOpenProject Foundation
        • Hierarchy leafBoards
        • Hierarchy leafMembers
        • Hierarchy leafOPF-Meetings
        • Hierarchy leafStatutes
      • Expanded. Click to collapseCollapsed. Click to showRelease Notes
        • Hierarchy leafOpenProject released on Bitnami
      • Expanded. Click to collapseCollapsed. Click to showRelease Notes OpenProject 40 - Overview
        • Hierarchy leafRelease Notes OpenProject 40 - Accessibility improvements
        • Hierarchy leafRelease Notes OpenProject 40 - Column header functions in work package table
        • Hierarchy leafRelease Notes OpenProject 40 - Improved Design
        • Hierarchy leafRelease Notes OpenProject 40 - Integrated query title on work package page
        • Hierarchy leafRelease Notes OpenProject 40 - Integrated toolbar on work package page
        • Hierarchy leafRelease Notes OpenProject 40 - OmniAuth integration for OpenProject
        • Hierarchy leafRelease Notes OpenProject 40 - Work package details pane
      • Expanded. Click to collapseCollapsed. Click to showSecurity and privacy
        • Hierarchy leafFAQ
      • Expanded. Click to collapseCollapsed. Click to showSupport
        • Expanded. Click to collapseCollapsed. Click to showDownload and Installation
          • Hierarchy leafInstallation MacOS
          • Expanded. Click to collapseCollapsed. Click to showInstallation OpenProject 3 0
            • Hierarchy leafDebian Stable with MySQL in production
            • Hierarchy leafInstallation Ubuntu
            • Hierarchy leafInstallation Windows
            • Hierarchy leafInstallation on Centos 65 x64 with Apache and PostgreSQL 93
          • Expanded. Click to collapseCollapsed. Click to showInstallation OpenProject 40
            • Hierarchy leafOP4 Debian Stable with MySQL in production
          • Expanded. Click to collapseCollapsed. Click to showMigration paths
            • Hierarchy leafFrom Chilliproject to OpenProject
            • Hierarchy leafMigration 15 to 30
            • Hierarchy leafMigration 24 to 30
            • Hierarchy leafMigration Redmine 2x › OpenProject 30
            • Hierarchy leafOpenProject 3 Migration
          • Hierarchy leafOpenProject 40
        • Expanded. Click to collapseCollapsed. Click to showNews
          • Hierarchy leafNew OpenProject Translations Plugin
          • Hierarchy leafNew Plugin on OpenProjectorg Local Avatars
          • Hierarchy leafNew design for OpenProject
          • Hierarchy leafNews Accessibility workshop for OpenProject
          • Hierarchy leafNews Glossary for OpenProject
          • Hierarchy leafNews Heartbleed fixed
          • Hierarchy leafNews Icon Fonts
          • Hierarchy leafNews OpenProject 30 Release
          • Hierarchy leafNews Release GitHub Integration Plugin
          • Hierarchy leafNews Success Story Deutsche Telekom
          • Hierarchy leafNews Timelines
          • Hierarchy leafOpenProject 3013 released
          • Hierarchy leafOpenProject 3017 released
          • Hierarchy leafOpenProject 40 released
          • Hierarchy leafOpenProject 40 will be coming soon
          • Hierarchy leafOpenProject 405 released
          • Hierarchy leafOpenProject and pkgrio
          • Hierarchy leafOpenProject news moved to a new blog
          • Hierarchy leafOpenProjectBitnami
          • Hierarchy leafPackager version with plugins released ("Community edition")
          • Hierarchy leafRegistration OpenProject-Foundation
          • Hierarchy leafRelease OpenProject AuthPlugins
          • Hierarchy leafUpdates on OpenProject
          • Hierarchy leafWe need your feedback for the the new fullscreen view for work packages
        • Hierarchy leafOpenProject Plug-Ins
      • Expanded. Click to collapseCollapsed. Click to showWiki
        • Hierarchy leaf2nd Level Support
You are here:
  • Forums
  • General discussion

Content

incoming email: creates new workpackage, but can't seem to update existing one

Added by Stan Cruise almost 6 years ago

Creating a new work package via an incoming email works well.

I have tried a number of things to update an existing work package, but all attempts result in the creation of a new work package.
I figured the allow_override is important to this, but so far I have not been able to make this update an existing one.

It looks like another simple thing staring me in the face :)

Can I indulge another excellent tip?

Stan


Replies (4)

RE: incoming email: creates new workpackage, but can't seem to update existing one - Added by Stan Cruise almost 6 years ago

I seem to have it working.

I had to reply to a notification email that I received by creating a work package.

Here is my sequence:

I created a new work package in Openproject.
In my separate email client, I then received the email notification.
I replied to this email, put status:Closed in the body, changed the to: address to the one the Openproject recognizes, and sent the email
This email I received in my external email client.
I moved this email into the box that I designate for Openproject to scan
I made the email ‘unread’ (learned this trick separately)
I went to Openproject; made sure I know the current status of the work package
Outside Openproject ran the rake task to scan the designated Openproject email box
Finally refreshed Openproject, and there is was: the status changed to Closed for the existing work package, and no new one was created!

I figured this out by searching Redmine for incoming email tricks. They had indicated to use the ‘issue #’ which Openproject does not seem to use.
But, then I stumbled on a description of simply replying to the email that Redmine sends out; so I did so for the Openproject email.

If this makes sense, it would be good to know.

If there is some other way to send in an update, then that would be good to know also.

However, I always send out emails for work package creation, etc, so I should always have the email to reply to.

Decoding the syntax for the reply email should be easy, and perhaps this is the route next.

Stan

RE: incoming email: creates new workpackage, but can't seem to update existing one - Added by Stan Cruise almost 6 years ago

Actually the reply email does contain the ID#, but it also has other elements. Pretty simple really.

RE: incoming email: creates new workpackage, but can't seem to update existing one - Added by Stan Cruise almost 6 years ago

Here is the subject line syntax I worked out for an update of an existing work package:

[ - Task #] ()

Gotchas:

The email in the designated box has to be unread

The status has to match

The send_from email address has to be correct (this was emphasized in the User Manual, but it is really easy to miss if one has >1 gmail accounts)

A forwarded email that automatically creates an attachment out of the forward text is not recognized as an attachment. If you really want the forwarded email text to be an attachment, you have to forward as an attachment, copy the attachment to a local dir, then manually attach this as a file. Then do the rake. The attachment looks the same, but OP then recognizes it as a file attachment.

Simply forwarding an email works just fine, but all the text appears in the update text of the work package. It is nicely formatted. So, this is the easiest route if you don’t mind a lot of scrolling.

All in all a very nice feature!

Now on to trying out other attributes.

RE: incoming email: creates new workpackage, but can't seem to update existing one - Added by B3 IT Systeme GmbH 2 months ago

The processing has changed in newer OpenProject versions.

OpenProject now creates appropriate headers in the email and processes these headers when replying or forwarding.

Example Headers:

X-OpenProject-Project: foo
X-OpenProject-Issue-Id: 123
X-OpenProject-Issue-Author: foo@bar.com
X-OpenProject-Type: WorkPackage
X-OpenProject-Issue-Assignee: foo@bar.com
X-Mailer: OpenProject
X-OpenProject-Host: foo.bar.com
X-OpenProject-Site: OpenProject

The subject of the email is no longer parsed at all.

See:
https://github.com/opf/openproject/blob/21a696ef9b170e14ad2daf53364a4c2113822c2f/app/models/mail_handler.rb#L148

  • (1 - 4/4)
Loading...