I am not sure what “incoming email functionality” is referring to,
however documentation on the API is available.
APIv3
Raw docs on the new APIv3 can be found in the codebase under doc: see here
APIv3 is documented in API Blueprint format, a rendered version for the dev-branch can be found here
The APIv3 and its documentation are currently considered drafts. This means things already documented might still change and new features will be added regularly.
The implementation and the specification might not be in sync 100%, because most things were specified before they were implemented.
Consider the current state of the APIv3 documentation as a preview.
APIv2
Documentation on the old APIv2 is maintained in our wiki: here
Note that we put our development effort into APIv3, this means that there will probably be no big changes to APIv2 anymore. In the long run APIv3 is supposed to replace APIv2 completely, meaning that v2 will be disabled eventually.
“Incoming mail functionality” refers to the ability to reply to notification e-mails (and have the reply posted at that work item / forum / whatever), or CC openproject with an e-mail and have the content appear there; or in general change (some) things through e-mail. The web API in unrelated.
Thanks, Jens. It actually looks very good in terms of functionality, I will try that and report.
There would be a few details, like setting the local part for notifications (openproject+task24@example.com) so that the e-mail could be simply replied-to without bothering about keeping the subject intact, but that’s minor.
Replies (7)
Any success? I’m looking for the same information as well.
May be worth looking into this wiki page http://www.redmine.org/projects/redmine/wiki/RedmineReceivingEmails
And then looking into openproject code base and compare if that redmine documentation can be applied to open project
Ping? I am very interested.
I am not sure what “incoming email functionality” is referring to,
however documentation on the API is available.
APIv3
Raw docs on the new APIv3 can be found in the codebase under
doc: see hereAPIv3 is documented in API Blueprint format, a rendered version for the dev-branch can be found here
The APIv3 and its documentation are currently considered drafts. This means things already documented might still change and new features will be added regularly.
The implementation and the specification might not be in sync 100%, because most things were specified before they were implemented.
Consider the current state of the APIv3 documentation as a preview.
APIv2
Documentation on the old APIv2 is maintained in our wiki: here
Note that we put our development effort into APIv3, this means that there will probably be no big changes to APIv2 anymore.
In the long run APIv3 is supposed to replace APIv2 completely, meaning that v2 will be disabled eventually.
I hope those links will help you.
Best regards
Jan Sandbrink
“Incoming mail functionality” refers to the ability to reply to notification e-mails (and have the reply posted at that work item / forum / whatever), or CC openproject with an e-mail and have the content appear there; or in general change (some) things through e-mail. The web API in unrelated.
Actually, what Episteme Partners states above is the sad truth. The best documentation for the functionality can AFAIK be found on the Redmine page.
There hasn’t been much work done on that functionality after forking from Redmine. The exception here is:
Following the page should get you up to speed.
Thanks, Jens. It actually looks very good in terms of functionality, I will try that and report.
There would be a few details, like setting the local part for notifications (openproject+task24@example.com) so that the e-mail could be simply replied-to without bothering about keeping the subject intact, but that’s minor.
Cheers!