Note that there are some explanatory texts on larger screens.

plurals
  1. POCreate Trac ticket from Google Form GAS script?
    primarykey
    data
    text
    <p>This is a followup question to my original question <a href="https://stackoverflow.com/questions/17950617/is-there-a-simple-bugzilla-trac-client-for-use-by-non-software-folks">here</a>. The decision between Bugzilla &amp; Trac seems to have been made for us, and Trac it is. Here are the options I've found so far: </p> <ul> <li><p>Leverage our current Google Form based bug report by modifying the GAS script that is doing our email notification. So far I've been unable to find an example, but it would appear that you can modify the email portion of the GAS script to send email to the Trac server to open a ticket automatically. This is my preferred option, but I'd like to see an example if possible. </p></li> <li><p>Create something using <a href="http://trac-hacks.org/wiki/TracCmdScript" rel="nofollow noreferrer">TracCmdScript</a>, but the site hasn't been updated in three years, and it appears to use python, a language I'm not proficient at (although I'd like to be) and the <a href="http://trac-hacks.org/wiki/XmlRpcPlugin" rel="nofollow noreferrer">XmlRpcPlugin</a>, which seems to be under current development.</p></li> <li><p>There's also an email option website cited on this SO page to use <a href="https://stackoverflow.com/questions/3926554/creating-trac-tickets-from-website">email2trac</a>, but the cited site appears to be dead. <strong>Edit</strong>: here's the new site: <a href="https://oss.trac.surfsara.nl/email2trac/wiki/Email2tracInstallation/Windows" rel="nofollow noreferrer">email2trac</a> which still hasn't been touched in a couple of years, but seems to be functional.</p></li> </ul> <p>I'm open to any other suggestions the SO folks might have.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload