The first module adds an option to configure the e-mail texts that the STS module is sending out. It also adds the all the custom e-mail strings to the i18n translatable interface for strings.
The issue can be found here: http://drupal.org/node/694264
The second module adds an option to define CCK fields for the content type that the STS module is using and the allow different 'Clients' in the STS module to use different fields.
The issue can be found here: http://drupal.org/node/676044
I would love to maintain these two add-on modules as I am the one who is primarily working on them and know them inside out. It would be a great way for me to give something back to the community which has proved itself so helpful so many times.
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | support_fields.zip | 2.86 KB | span |
Comments
Comment #1
span commentedThe first module in still under development and thus you can ignore that.
Attached with this application is the finished module that handles CCK field options for the specific Clients in the STS module. That is the second module I mention in my application.
Comment #2
avpadernoHello, and thanks for applying for a CVS account. I am adding the review tags, and some volunteers will review your code, pointing out what needs to be changed.
As per http://drupal.org/cvs-application/requirements, the motivation should be expanded, and include more details about the features implemented by the module, and a comparison with the existing solutions.
Comment #3
span commentedHello
Sorry for not being descriptive enough in my original application. I've expanded on it as follows:
The Support Ticketing System module adds great functionality for handling strict support errands. The STS module puts all the content in the body and title field and this is sufficient for a lot of users but there are requests for more flexibility.
This module expands on that to allow multiple fields to be added to the content type of the support ticket. This could be very useful for websites who wish to make sure that more detailed information can be provided to each support ticket that just a problem description. One could add a customer number field, telephone number, select lists of different products on which the support is to be given for example.
I can't really compare this to existing solutions since there are none. These are requests that have come up recently and it was a feature I needed as well so I decided to implement it. Jeremy who is the maintainer of STS is planning on doing this for the Drupal 7 version only since it has fields in the core and he asked me to turn my code which implements this feature in Drupal 6 into an add-on for STS.
The module works as such:
You add custom CCK fields to the STS content type.
You can then go into the STS Client* settings to choose which fields to display for which Clients.
This will change the node-edit form for this specific content type to show or hide the fields on ticket creation/editing.
The support ticket will then render the appropriate fields to the users for viewing.
* Clients are like categories in the STS module.
To test it you must:
1) Install Support Ticketing System (http://drupal.org/project/support) and the attached add-on module (http://drupal.org/node/726644#comment-2649950)
2) Add a custom field to the content type provided by STS
3) Set permissions on that field
4) Create a Client in STS
5) Go to the settings page for the client to set which fields to hide/display
6) Review the node-edit form
7) Review the generated node
8) Repeat 2-7 for additional fields
Comment #4
avpadernoComment #5
avpadernoThank you for your contribution! I am going to update your account.
These are some recommended readings to help with excellent maintainership:
You can find more contributors chatting on the IRC #drupal-contribute channel. So, come hang out and stay involved.
Thank you, also, for your patience with the review process.
Anyone is welcome to participate in the review process. Please consider reviewing other projects that are pending review. I encourage you to learn more about that process and join the group of reviewers.
I thank all the dedicated reviewers as well.
Comment #8
avpaderno