Trouble Ticket block: Difference between revisions
From MoodleDocs
Jason Hardin (talk | contribs) (New page: =Block Description= The trouble ticket block was developed to provide Moodle users with a simple way to notify Moodle site administrators of a problem with the site or a specific module o...) |
Helen Foster (talk | contribs) m (categories tidy up) |
||
| (One intermediate revision by one other user not shown) | |||
| Line 3: | Line 3: | ||
The trouble ticket block was developed to provide Moodle users with a simple way to notify Moodle site administrators of a problem with the site or a specific module or block. The trouble ticket block allows Teachers to add multiple types of trouble tickets to a page as either a link or a button. Each Trouble ticket can be configured with a specific email to send the notification to as well as a custom response to the user. | The trouble ticket block was developed to provide Moodle users with a simple way to notify Moodle site administrators of a problem with the site or a specific module or block. The trouble ticket block allows Teachers to add multiple types of trouble tickets to a page as either a link or a button. Each Trouble ticket can be configured with a specific email to send the notification to as well as a custom response to the user. | ||
'''Developers''' | |||
Moodlerooms Inc., Mike Avelar, Sam Chaffee, Jason Hardin, Mark Nielsen | Moodlerooms Inc., Mike Avelar, Sam Chaffee, Jason Hardin, Mark Nielsen | ||
[[Category:Block]] | [[Category:Block]] | ||
[[Category:Contributed code]] | [[Category:Contributed code]] | ||
Latest revision as of 06:46, 15 October 2011
Block Description
The trouble ticket block was developed to provide Moodle users with a simple way to notify Moodle site administrators of a problem with the site or a specific module or block. The trouble ticket block allows Teachers to add multiple types of trouble tickets to a page as either a link or a button. Each Trouble ticket can be configured with a specific email to send the notification to as well as a custom response to the user.
Developers Moodlerooms Inc., Mike Avelar, Sam Chaffee, Jason Hardin, Mark Nielsen
