% has_contexts = !current_user.contexts.empty? -%>
Tracks can be integrated with a number of other tools... whatever it takes to help you get things done! This page has information on setting up some of these. Not all of these are applicable to all platforms, and some require more technical knowledge than others. See also <%= link_to "developer documentation for Tracks' REST API", url_for(:action => 'rest_api') %>.
Contents:
Do you have one of your own to add? Tell us about it in our Tips and Tricks forum and we may include it on this page in a future versions of Tracks.
If you enter the following entry to your crontab, you will receive email every day around 5 AM with a list of the upcoming actions which are due within the next 7 days.
You can of course use other text <%= link_to 'feeds provided by Tracks', feeds_path %> -- why not email a list of next actions in a particular project to a group of colleagues who are working on the project?
If Tracks is running on the same server as your mail server, you can use the integrated mail handler built into tracks. Steps to set it up:
/PATH/TO/TRACKS/bin/rails r -e production 'MessageGateway.receive(STDIN.read)'
You can also use the Rich Todo API to send in tasks like "do laundry @ Home" or "Call Bill > project X". The subject of the message will fill description, context, and project, while the body will populate the tasks's note.
You may need to configure your site.yml to tell the message gateway to look at the to: field or from: field to lookup Tracks' user from the email address in that field.
You can also send all email to a specific Tracks user. Configure mail_dispatch in site.yml to single_user and pass the login of the user:
TRACKS_MAIL_RECEIVER=<%=current_user.login%> /PATH/TO/TRACKS/bin/rails r -e production 'MessageGateway.receive(STDIN.read)'
If you want to email tasks to Tracks, but cannot run a mailserver on the same host, you could use the Mailgun support built in to Tracks.
For this to work your Tracks server will need to be reachable from the internet, so that Mailgun can POST data to it.
mailmap: tracks@user.mailgun.org: - me@myhome.domain.net - mr.user@work.company.com
All the comments about the email format from the section above apply to the Mailgun handling, as the data is processed the same way
For both of the above methods, the follow format can be used:
my awesome todo @context ~project <131012 >131009 #tag1 #tag2 *
The fields are:
| Symbol | Meaning |
|---|---|
| @ | The context to place the Todo in |
| ~ | The project to place the Todo in |
| < | The due date for the Todo (may be 2 digits for day, 4 digits for month-day, or 6 digits for yeah-month-day) |
| > | The due date for the Todo (may be 2 digits for day, 4 digits for month-day, or 6 digits for yeah-month-day) |
| # | A tag to apply to the Todo - may be used multiple times |
| * | Flag to star the Todo |
All symbols are optional, and text up to the first symbol (or end of string) is used as the description of the todo
You can now manage your projects/actions inside Gmail using Tracks Gmail Gadget. Add Tracks Gmail gadget to the sidebar of Gmail and track your next actions or add new action without explicitly open new browser tab for Tracks. Steps to set it up:
<%= integrations_url + "/google_gadget" %>