Issue

Issues are stored in JSON files of the following format:

{"energy": "4", "index": "20130820173706", "priority": "4", "status": "N", "summary": "Buy the milk!", "time": "4"}

1. Index. Index is somewhat similar to a timestamp of issue creation, assuming that issues aren’t created more often than once a second — they are unique. Index could be represented as follows: YYYYMMDDHHMMSS.
2. Status. This field stores the status of the issue. It can take one of the two possible values: N ( next ) and S ( someday ). Each of the values correspond to certain status in the GTD system. It also takes D and C now, but these statuses can’t be assigned on edit, only using special commands done and cancel.
3. Priority. Priority of the issue from 1 to 5.
4. Energy. Ammount of energy that accomplishing the issue from 1 to 5.
5. Time. How much time this issue may take to complete. In number of sessions or zero, if the progress will take less, than ordinary working session. Session is a time period of concentrated work. It may be anything from 10 minutes to a couple of hours. Don’t forget to make short breaks between sessions.
6. Summary. Short description of the issue.

Name of the XML file that the issue is written to is the same as the issue index. Basically indexes are unique identifiers.