•  
     
    story #6256 to be able to create an artifact by sending an email to trackerXXXX@tuleapserver.com
Summary
Tuleap User
to be able to create an artifact by sending an email to trackerXXXX@tuleapserver.com
- I can use this feature in automated testing to create bug artifacts, for failed test cases.
- I can set up Outlook rules to automatically create an artifact based on a given email. For example, for emails generated by our internal IT Support system when tickets are created by end-users.

Follow-up art #8431 and art #8432

Email sent by the user

Given a mail sent by a user with a regular MUA (Outlook or whatever)

  • From: email
  • To: tracker534@tuleapserver.com
  • Subject:
  • Body

A new artifact will be created in tracker 534 as long as:

  • the email address corresponds to one uniq user in Tuleap DB and this user is allowed to create artifacts (with permissions on corresponding fields)
    • if email is not uniq, a notification is sent to the email, the artifact is not created
  • there is a Title semantic on the tracker (for the subject)
  • there is a Description semantic on the tracker (for the body of the email)
  • there is no other "Required" fields on submit (default values apply for other fields)
    • only the text/plain part of the message will be used (as of today)
  • When all condition are met, a link is displayed to the user so that we know he can create art by mail

When all the conditions are met, artifact is created with all artifact features (notifications & co)

Empty
Domenico Alessi (domale), Emilio Palmiero (empa)
Status
Empty
Done
Development
  • [ ] Does it involves User Interface? 
  • [ ] Are there any mockups?
  • [ ] Are permissions checked?
  • [ ] Does it need Javascript development?
  • [ ] Does it need a forge upgrade bucket?
  • [ ] Does it need to execute things in system events?
  • [ ] Does it impact project creation (templates)?
  • [ ] Is it exploratory?
Empty
Details
#6256
Patricia Carrasco (pcar)
2015-10-29 12:04
2014-02-19 20:28
8529

References

Follow-ups

User avatar
Emilio Palmiero (empa)2015-09-21 20:18
  • So that
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes
User avatar
  • Acceptance criteria
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes
User avatar
  • Acceptance criteria
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes
User avatar
  • Acceptance criteria
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes
User avatar
  • Acceptance criteria
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes
User avatar
  • Acceptance criteria
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes
User avatar
  • Acceptance criteria
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes
User avatar
Emilio,

I updated the description according to our discussion yesterday, does it fullfill your needs ?

On my site, I have a few questions:
- could you detail what you expect by "The use of the message headers also would allow from an end user and tuleap server perspective an easy way to filter on this emails."
- could you fill the "In order to" section with a concrete use case ?

Thanks

  • I want to
    -to be able to create an artifact or add a comment by sending an email to trackerXXXX@tuleapserver.com 
    +to be able to create an artifact by sending an email to trackerXXXX@tuleapserver.com 
  • So that
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes
  • Acceptance criteria
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes
User avatar
  • So that
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes
  • Acceptance criteria
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes
User avatar
  • So that
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes