#6708 Handle trac cc field

v1.1.0
closed
Tim Van Steenburgh
import (116) trac (14) sf-1 (616)
General
Cory Johns
2015-08-20
2013-09-24
Dave Brondsema
No

We currently import the CC field as a custom field. We shouldn't do that at all, it's useless like that. We should also convert it to a subscription if possible, but we don't know the full email address and if we did it may not match an Allura user. A halfway solution might be to consider each CC as a vote.

https://sourceforge.net/apps/trac/mcclidar/ticket/33 is one example. Don't have an example of multiple CCs handy

Discussion

  • Dave Brondsema

    Dave Brondsema - 2013-10-04
    • Description has changed:

    Diff:

    --- old
+++ new
@@ -1,3 +1,3 @@
 We currently import the CC field as a custom field.  We shouldn't do that at all, it's useless like that.  We should also convert it to a subscription if possible, but we don't know the full email address and if we did it may not match an Allura user.  A halfway solution might be to consider each CC as a vote.
-
+    
 https://sourceforge.net/apps/trac/mcclidar/ticket/33 is one example.  Don't have an example of multiple CCs handy
    • Size: --> 1
     

  • Dave Brondsema

    Dave Brondsema - 2013-10-04

    For now lets just do the easy fix of not making this field a custom field at all. Ignore it.

     

  • Dave Brondsema

    Dave Brondsema - 2013-10-04
    • Milestone: forge-oct-18 --> forge-nov-01
     

  • Tim Van Steenburgh - 2013-10-23
    • status: open --> in-progress
    • assigned_to: Tim Van Steenburgh
     

  • Tim Van Steenburgh - 2013-10-23
    • status: in-progress --> code-review
     

  • Cory Johns - 2013-10-24
    • status: code-review --> closed
    • QA: Cory Johns
     

Log in to post a comment.