|
32 |
✓invalid |
Write tests for generators |
Gemini XI |
Christopher Peplin |
about 15 years old |
|
48 |
✓resolved |
Write views for basic CRUD operations, no styling |
Gemini IX-A |
Christopher Peplin |
about 15 years old |
|
52 |
✓resolved |
Write controller tests for admin indices - should list game wide stats |
Gemini IX-A |
Christopher Peplin |
about 15 years old |
|
57 |
✓resolved |
Rename region to state, zone to city |
Gemini IV |
Christopher Peplin |
about 15 years old |
|
59 |
✓resolved |
Add URLs relying on current game in cookie |
Gemini IV |
Christopher Peplin |
about 15 years old |
|
56 |
✓resolved |
Set game in cookie to simplify URLs (but don't delete them) |
Gemini IV |
Christopher Peplin |
about 15 years old |
|
40 |
✓resolved |
Add 'last updated' field to game |
Gemini V |
Christopher Peplin |
about 15 years old |
|
50 |
✓resolved |
Simplify contract controller and models |
Gemini IV |
Christopher Peplin |
about 15 years old |
|
51 |
✓resolved |
Simplify repairs if they truly are meant for all technical components |
Gemini IV |
Christopher Peplin |
about 15 years old |
|
54 |
✓resolved |
Hook up login system |
Gemini III |
Christopher Peplin |
about 15 years old |
|
47 |
✓resolved |
Write controllers for basic CRUD operations |
Gemini III |
Christopher Peplin |
about 15 years old |
|
46 |
✓resolved |
Tests for views for model management |
Gemini III |
Christopher Peplin |
about 15 years old |
|
43 |
✓resolved |
Add tests for controllers for models |
Mercury-Atlas 12 |
Christopher Peplin |
about 15 years old |
|
49 |
✓resolved |
Make URLs hackable in web interface |
Mercury-Atlas 11 |
Christopher Peplin |
about 15 years old |
|
45 |
✓invalid |
Add tests for controllers |
Mercury-Atlas 11 |
Christopher Peplin |
about 15 years old |
|
44 |
✓resolved |
Add route specs |
Mercury-Atlas 11 |
Christopher Peplin |
about 15 years old |
|
37 |
✓resolved |
Write database migrations for economic components |
Mercury-Atlas 8 |
Christopher Peplin |
about 15 years old |
|
36 |
✓resolved |
Write database migrations for map components |
Mercury-Atlas 8 |
Christopher Peplin |
about 15 years old |
|
35 |
✓resolved |
Write database migrations for technical components |
Mercury-Atlas 8 |
Christopher Peplin |
about 15 years old |
|
26 |
✓resolved |
Choose map generation algorithm |
Mercury-Atlas 8 |
Christopher Peplin |
about 15 years old |
|
30 |
✓resolved |
Design workflow and data models for growing the region |
Mercury-Atlas 7 |
Christopher Peplin |
about 15 years old |
|
29 |
✓resolved |
Design contract parameters and data model |
Mercury-Atlas 7 |
Christopher Peplin |
about 15 years old |
|
24 |
✓resolved |
Decide on best database backend |
Mercury-Atlas 8 |
Christopher Peplin |
about 15 years old |
|
23 |
✓resolved |
Design workflow for inviting user to a private/public multiplayer game |
Mercury-Atlas 7 |
Christopher Peplin |
about 15 years old |
|
22 |
✓resolved |
Design workflow for creating a public game |
Mercury-Atlas 7 |
Christopher Peplin |
about 15 years old |
|
28 |
✓resolved |
Revisit real-time behavior |
Mercury-Atlas 6 |
Christopher Peplin |
about 15 years old |
|
27 |
✓resolved |
Decide if a background daemon is required |
Mercury-Atlas 6 |
Christopher Peplin |
about 15 years old |
|
25 |
✓resolved |
Diagram data model |
Mercury-Atlas 6 |
Christopher Peplin |
about 15 years old |
|
21 |
✓resolved |
Design relationship between user and a map region |
Mercury-Atlas 7 |
Christopher Peplin |
about 15 years old |
|
20 |
✓resolved |
Design relationship between user account and a game |
Mercury-Atlas 7 |
Christopher Peplin |
about 15 years old |
Create new ticket