Agile based tracker
Ruby CSS JavaScript CoffeeScript
Latest commit cab6b46 Jun 17, 2014 @mandelbroat mandelbroat Merge pull request #28 from rrrene/patch-2
Update docs badge in README
Failed to load latest commit information.
config update gems Mar 31, 2014
db Solving bad pratices Apr 20, 2013
lib removing unused config Mar 18, 2012
log add rails 3.1 skeleton May 12, 2011
public #39 Added logo and favicon Jul 22, 2011
script first commit drunk Apr 7, 2011
spec fixing logout button May 15, 2014
vendor updating gems Mar 31, 2014
.gitignore Removing gems from vendor/cache =p Aug 27, 2012
.travis.yml add support to ruby v2.1.2 May 10, 2014
Gemfile locking all versions on gems Mar 31, 2014
Gemfile.lock locking all versions on gems Mar 31, 2014
README.markdown Update docs badge in README Jun 17, 2014
Rakefile first commit drunk Apr 7, 2011


Startrack Tracker: Build Status Code Climate Inline docs

What is it?

This is a SaaS project that intend to help agile teams through the a KanBan-like dashboard to manage projects, tasks and teams.


This code is free to be used under the terms of the GNU General Public License.

Bugs, Issues, Kudos and Catcalls

Comments are welcome. Send your feedback through the issue tracker on GitHub


We have a list of contributors. Check them all at: Contributors

Suggested features:

  • Organization account
  • Team members CRUD
  • Project CRUD
    • Show project status
  • User story CRUD
    • User Story has a total of tasks points
    • Show Finished Stories
    • Group Stories
    • Attach files to Stories
    • A Story may be accepted or not
    • Add Acceptance testing to a Story
  • Task CRUD
    • User Story has many tasks
    • Each Task has status (done, new, assigned, etc)
    • Each Task has type (feature, bug, etc)
    • Each Task may has a owner
  • Define Product Backlog
  • Define Sprint Backlog
  • Define workflow
  • Priorize user stories
  • Team velocity
  • Show burndown chart

To discuss

  1. Organizations will have a limit of projects
  2. Projects will have a max number of users
  3. Change Story priority after starts the sprint
  4. Define de DOD (Do Of Done) for a project
  5. Pair programing for teams
  6. Team alert for new entries on a User Story
  7. Use github API to use github issues as Startrack task syncing