Giter Site home page Giter Site logo

fulcrum-agile / fulcrum Goto Github PK

View Code? Open in Web Editor NEW
1.5K 76.0 351.0 2.19 MB

An agile project planning tool

Home Page: http://wholemeal.co.nz/projects/fulcrum.html

License: GNU Affero General Public License v3.0

Ruby 39.62% JavaScript 46.67% HTML 8.02% EJS 1.17% SCSS 4.51%

fulcrum's Introduction

Fulcrum

Project no longer maintained

This project is no longer maintained. At the time of writing there is an active fork at https://github.com/Codeminer42/cm42-central - please check out that project if you are looking for a similar tool.


Fulcrum is an application to provide a user story based backlog management system for agile development teams. See the project page for more details.

Build Status

Fulcrum Screenshot

Get involved

Fulcrum is still in early development, so now is the time to make your mark on the project.

There are several communication channels for Fulcrum:

See the Development section below for details on contributing to the project, and Translating for details on how to help translate Fulcrum into your native language.

Goals

Fulcrum is a clone of Pivotal Tracker. It will almost certainly never surpass the functionality, usability and sheer awesomeness of Pivotal Tracker, but aims to provide a usable alternative for users who require a Free and Open Source solution.

Installation

Fulcrum is still a work in progress, but if you're really keen to try it out these instructions will hopefully help you get up and running.

First up, your system will need the prerequisites for running Ruby on Rails installed

Once you have these:

# Checkout the project
$ git clone git://github.com/fulcrum-agile/fulcrum.git
$ cd fulcrum

# Install the project dependencies
$ gem install bundler
$ bundle install

# Set up the development database
$ bundle exec rake fulcrum:setup db:setup

# Start the local web server
$ rails server

You should then be able to navigate to http://localhost:3000/ in a web browser. You can log in with the test username [email protected], password testpass.

Heroku setup

If you wish to host a publicly available copy of Fulcrum, the easiest option is to host it on Heroku.

To deploy it to Heroku, make sure you have a local copy of the project; refer to the previous section for instructions. Then:

$ gem install heroku

# Create your app. Replace APPNAME with whatever you want to name it.
$ heroku create APPNAME --stack cedar-14

# Set APP_HOST heroku config so outbound emails have a proper host
# Replace APPNAME below with the value from `heroku create`
$ heroku config:set APP_HOST=APPNAME.herokuapp.com

# Define where the user emails will be coming from
# (This email address does not need to exist)
$ heroku config:set [email protected]

# Tell Heroku to exclude parts of the Gemfile
$ heroku config:set BUNDLE_WITHOUT='development:test:travis:mysql:sqlite'

# Allow emails to be sent
$ heroku addons:add sendgrid:starter

# Deploy the first version
$ git push heroku master

# Set up the database
$ heroku run rake db:setup

Once that's done, you will be able to view your site at http://APPNAME.herokuapp.com.

Deploying to other platforms

Fulcrum can be deployed to any platform that can host Rails. Setting this up is beyond the scope of this document, but for the most part Fulcrum does not have any special operational requirements and can be deployed as a normal Rails application.

You will need to set up some custom configuration, to do this copy the file config/fulcrum.example.rb to config/fulcrum.rb and edit to your requirements, or ensure the relevant environment variables are set for the application as described in the file above.

Translating

Below is an example of how you might go about translating Fulcrum to German.

  • Find the name of your locale, in this case we are using de
  • Copy the config/locales/en.yml file to config/locales/de.yml
  • Edit the file and update all the translated strings in quotes on the right hand side.
  • Add your new locale to config.i18n.available_locales in config/application.rb
  • Run rake i18n:js:export to build the Javascript translations.

Thats it! Ideally you should send your translation as a pull request so you get credit for it, but if you do not wish to do this please send the file to one of the mailing lists.

If Fulcrum has already been translated for your language, please take the time to check the translation database is complete for your language. You can do this by running the rake i18n:missing_keys task. If you find any missing keys for your language please add them.

Development

Fulcrum is currently welcoming contributions. If you'd like to help:

  • Check the issue queue for a list of the major features which are yet to be implemented. These have the feature and unstarted labels. If a feature you'd like to work on isn't there, add an issue.
  • Leave a description of how you are going to implement the feature. Failure to do this may lead to you implementing the feature in a way that might conflict with future plans for Fulcrum, and so increase the chances of your work being rejected or needing a rework.
  • If you'd like to discuss anything about the issue in greater detail with other developers, do so on the Fulcrum Developers mailing list.

Here are some general guidelines for contributing:

  • Make your changes on a branch, and use that branch as the base for pull requests.
  • Try to break changes up into the smallest logical blocks possible. We'd prefer to receive many small commits to one large one in a pull request.
  • Feel free to open unfinished pull requests if you'd like to discuss work in progress, or would like other developers to test it.
  • All patches changes be covered by tests, and should not break the existing tests, unless a current test is invalidated by a code change. This includes Javascript, which is covered with a Jasmine test suite in spec/javascripts/.
  • Run rake spec to check the Rails test suite is green. You will need Firefox with Selenium installed to run the integration tests.
  • To run the Javascript test suite, run rails server and point your browser to http://localhost:3000/specs or run rake spec:javascripts
  • For any UI changes, please try to follow the Tango theme guidelines.
  • The easiest way to test the impact of CSS or view changes is using the 'testcard' at http://localhost:3000/testcard. This is a fake project which exposes as many of the view states as possible on one page.

Colophon

Fulcrum is built with the following Open Source technologies:

License

Copyright 2011-2015, Malcolm Locke.

Fulcrum is made available under the Affero GPL license version 3, see LICENSE.txt.

fulcrum's People

Contributors

aupajo avatar bradleypriest avatar coffeesam avatar davidakachaos avatar dstockdale avatar hakunin avatar iandouglas avatar jasnow avatar jasonbuehler avatar jgarcia avatar jrgifford avatar kaleworsley avatar kidach1 avatar komagata avatar kwgch avatar marnen avatar merodriguezblanco avatar pablodon avatar pachkovsky avatar parndt avatar patrickdavey avatar rioki avatar rodel30 avatar rstacruz avatar ryanbriones avatar sanemat avatar suer avatar unixmonkey avatar yrb avatar zakharday avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

fulcrum's Issues

Wrong link for confirmation instructions

Hey there,

In my installation, when I go to http://.../users/password/edit?reset_password_token=BLAHBLAH (password recovery), there shows a link to a non-existant page:

Didn't receive confirmation instructions?
--> http://.../users/confirmation/new

I don't know if it's only me or other people also have the same issue.

Cheers!
F3r

Install issue: method missing

I was following the install instructions when I got this:

root@machine:~/fulcrum# bundle exec rake fulcrum:setup db:setup
cp /root/fulcrum/config/database.yml.example /root/fulcrum/config/database.yml
db/test.sqlite3 already exists
db/development.sqlite3 already exists
-- create_table("changesets", {:force=>true})
   -> 0.0708s
-- create_table("notes", {:force=>true})
   -> 0.0152s
-- create_table("projects", {:force=>true})
   -> 0.0919s
-- create_table("projects_users", {:id=>false, :force=>true})
   -> 0.0237s
-- create_table("stories", {:force=>true})
   -> 0.0416s
-- create_table("users", {:force=>true})
   -> 0.0345s
-- add_index("users", ["confirmation_token"], {:name=>"index_users_on_confirmation_token", :unique=>true})
   -> 0.0268s
-- add_index("users", ["email"], {:name=>"index_users_on_email", :unique=>true})
   -> 0.0437s
-- add_index("users", ["reset_password_token"], {:name=>"index_users_on_reset_password_token", :unique=>true})
   -> 0.0277s
-- initialize_schema_migrations_table()
   -> 0.0560s
-- assume_migrated_upto_version(20111009095221, "db/migrate")
   -> 0.3260s
xprop:  unable to open display ''
/var/lib/gems/1.9.1/gems/activesupport-3.0.11/lib/active_support/whiny_nil.rb:48:in `method_missing': undefined method `shellsplit' for nil:NilClass (NoMethodError)
    from /var/lib/gems/1.9.1/gems/launchy-2.0.5/lib/launchy/detect/runner.rb:41:in `shell_commands'
    from /var/lib/gems/1.9.1/gems/launchy-2.0.5/lib/launchy/detect/runner.rb:104:in `block in wet_run'
    from /var/lib/gems/1.9.1/gems/launchy-2.0.5/lib/launchy/detect/runner.rb:103:in `fork'
    from /var/lib/gems/1.9.1/gems/launchy-2.0.5/lib/launchy/detect/runner.rb:103:in `wet_run'
    from /var/lib/gems/1.9.1/gems/launchy-2.0.5/lib/launchy/detect/runner.rb:61:in `run'
    from /var/lib/gems/1.9.1/gems/launchy-2.0.5/lib/launchy/application.rb:58:in `run'
    from /var/lib/gems/1.9.1/gems/launchy-2.0.5/lib/launchy/applications/browser.rb:76:in `open'
    from /var/lib/gems/1.9.1/gems/launchy-2.0.5/lib/launchy.rb:30:in `open'
    from /var/lib/gems/1.9.1/gems/letter_opener-0.0.2/lib/letter_opener/delivery_method.rb:12:in `deliver!'
    from /var/lib/gems/1.9.1/gems/mail-2.2.19/lib/mail/message.rb:1989:in `do_delivery'
    from /var/lib/gems/1.9.1/gems/mail-2.2.19/lib/mail/message.rb:230:in `block in deliver'
    from /var/lib/gems/1.9.1/gems/actionmailer-3.0.11/lib/action_mailer/base.rb:426:in `block in deliver_mail'
    from /var/lib/gems/1.9.1/gems/activesupport-3.0.11/lib/active_support/notifications.rb:52:in `block in instrument'
    from /var/lib/gems/1.9.1/gems/activesupport-3.0.11/lib/active_support/notifications/instrumenter.rb:21:in `instrument'
    from /var/lib/gems/1.9.1/gems/activesupport-3.0.11/lib/active_support/notifications.rb:52:in `instrument'
    from /var/lib/gems/1.9.1/gems/actionmailer-3.0.11/lib/action_mailer/base.rb:424:in `deliver_mail'
    from /var/lib/gems/1.9.1/gems/mail-2.2.19/lib/mail/message.rb:230:in `deliver'
    from /var/lib/gems/1.9.1/gems/devise-1.2.1/lib/devise/models/confirmable.rb:50:in `send_confirmation_instructions'
    from /var/lib/gems/1.9.1/gems/activesupport-3.0.11/lib/active_support/callbacks.rb:423:in `_run_create_callbacks'
    from /var/lib/gems/1.9.1/gems/activerecord-3.0.11/lib/active_record/callbacks.rb:277:in `create'
    from /var/lib/gems/1.9.1/gems/activerecord-3.0.11/lib/active_record/persistence.rb:257:in `create_or_update'
    from /var/lib/gems/1.9.1/gems/activerecord-3.0.11/lib/active_record/callbacks.rb:273:in `block in create_or_update'
    from /var/lib/gems/1.9.1/gems/activesupport-3.0.11/lib/active_support/callbacks.rb:424:in `_run_save_callbacks'
    from /var/lib/gems/1.9.1/gems/activerecord-3.0.11/lib/active_record/callbacks.rb:273:in `create_or_update'
    from /var/lib/gems/1.9.1/gems/activerecord-3.0.11/lib/active_record/persistence.rb:60:in `save!'
    from /var/lib/gems/1.9.1/gems/activerecord-3.0.11/lib/active_record/validations.rb:49:in `save!'
    from /var/lib/gems/1.9.1/gems/activerecord-3.0.11/lib/active_record/attribute_methods/dirty.rb:30:in `save!'
    from /var/lib/gems/1.9.1/gems/activerecord-3.0.11/lib/active_record/transactions.rb:245:in `block in save!'
    from /var/lib/gems/1.9.1/gems/activerecord-3.0.11/lib/active_record/transactions.rb:292:in `block in with_transaction_returning_status'
    from /var/lib/gems/1.9.1/gems/activerecord-3.0.11/lib/active_record/connection_adapters/abstract/database_statements.rb:139:in `transaction'
    from /var/lib/gems/1.9.1/gems/activerecord-3.0.11/lib/active_record/transactions.rb:207:in `transaction'
    from /var/lib/gems/1.9.1/gems/activerecord-3.0.11/lib/active_record/transactions.rb:290:in `with_transaction_returning_status'
    from /var/lib/gems/1.9.1/gems/activerecord-3.0.11/lib/active_record/transactions.rb:245:in `save!'
    from /var/lib/gems/1.9.1/gems/activerecord-3.0.11/lib/active_record/validations.rb:34:in `create!'
    from /root/fulcrum/db/seeds.rb:3:in `<top (required)>'
    from /var/lib/gems/1.9.1/gems/activesupport-3.0.11/lib/active_support/dependencies.rb:235:in `load'
    from /var/lib/gems/1.9.1/gems/activesupport-3.0.11/lib/active_support/dependencies.rb:235:in `block in load'
    from /var/lib/gems/1.9.1/gems/activesupport-3.0.11/lib/active_support/dependencies.rb:225:in `block in load_dependency'
    from /var/lib/gems/1.9.1/gems/activesupport-3.0.11/lib/active_support/dependencies.rb:593:in `new_constants_in'
    from /var/lib/gems/1.9.1/gems/activesupport-3.0.11/lib/active_support/dependencies.rb:225:in `load_dependency'
    from /var/lib/gems/1.9.1/gems/activesupport-3.0.11/lib/active_support/dependencies.rb:235:in `load'
    from /var/lib/gems/1.9.1/gems/activerecord-3.0.11/lib/active_record/railties/databases.rake:290:in `block (2 levels) in <top (required)>'
    from /var/lib/gems/1.9.1/gems/rake-0.9.2.2/lib/rake/task.rb:205:in `call'
    from /var/lib/gems/1.9.1/gems/rake-0.9.2.2/lib/rake/task.rb:205:in `block in execute'
    from /var/lib/gems/1.9.1/gems/rake-0.9.2.2/lib/rake/task.rb:200:in `each'
    from /var/lib/gems/1.9.1/gems/rake-0.9.2.2/lib/rake/task.rb:200:in `execute'
    from /var/lib/gems/1.9.1/gems/rake-0.9.2.2/lib/rake/task.rb:158:in `block in invoke_with_call_chain'
    from /usr/lib/ruby/1.9.1/monitor.rb:201:in `mon_synchronize'
    from /var/lib/gems/1.9.1/gems/rake-0.9.2.2/lib/rake/task.rb:151:in `invoke_with_call_chain'
    from /var/lib/gems/1.9.1/gems/rake-0.9.2.2/lib/rake/task.rb:176:in `block in invoke_prerequisites'
    from /var/lib/gems/1.9.1/gems/rake-0.9.2.2/lib/rake/task.rb:174:in `each'
    from /var/lib/gems/1.9.1/gems/rake-0.9.2.2/lib/rake/task.rb:174:in `invoke_prerequisites'
    from /var/lib/gems/1.9.1/gems/rake-0.9.2.2/lib/rake/task.rb:157:in `block in invoke_with_call_chain'
    from /usr/lib/ruby/1.9.1/monitor.rb:201:in `mon_synchronize'
    from /var/lib/gems/1.9.1/gems/rake-0.9.2.2/lib/rake/task.rb:151:in `invoke_with_call_chain'
    from /var/lib/gems/1.9.1/gems/rake-0.9.2.2/lib/rake/task.rb:144:in `invoke'
    from /var/lib/gems/1.9.1/gems/rake-0.9.2.2/lib/rake/application.rb:116:in `invoke_task'
    from /var/lib/gems/1.9.1/gems/rake-0.9.2.2/lib/rake/application.rb:94:in `block (2 levels) in top_level'
    from /var/lib/gems/1.9.1/gems/rake-0.9.2.2/lib/rake/application.rb:94:in `each'
    from /var/lib/gems/1.9.1/gems/rake-0.9.2.2/lib/rake/application.rb:94:in `block in top_level'
    from /var/lib/gems/1.9.1/gems/rake-0.9.2.2/lib/rake/application.rb:133:in `standard_exception_handling'
    from /var/lib/gems/1.9.1/gems/rake-0.9.2.2/lib/rake/application.rb:88:in `top_level'
    from /var/lib/gems/1.9.1/gems/rake-0.9.2.2/lib/rake/application.rb:66:in `block in run'
    from /var/lib/gems/1.9.1/gems/rake-0.9.2.2/lib/rake/application.rb:133:in `standard_exception_handling'
    from /var/lib/gems/1.9.1/gems/rake-0.9.2.2/lib/rake/application.rb:63:in `run'
    from /var/lib/gems/1.9.1/gems/rake-0.9.2.2/bin/rake:33:in `<top (required)>'
    from /var/lib/gems/1.9.1/bin/rake:19:in `load'
    from /var/lib/gems/1.9.1/bin/rake:19:in `<main>'

It is an instance at Amazon, with 64-bit Ubuntu 11.10. It may also be worth noting that the install tries to run xprop right before the error occurs, but of course there is no display.

Any help would be appreciated, thanks!

Rails default validations not working

Error when running migrations from validates method in story.rb

When i am trying to set up the app and run the migrations i am getting this error : You need to supply at least one validation.

Initial guess was that somewhere there's a validates instead of a validate. But when i do a ack , i don't see anything weird. They are all normal rails validations. Version of rails is 3.0.11. The error is thrown from here : ~/.rvm/gems/ruby-1.8.7-p352@fulcrum/gems/activemodel-3.0.11/lib/active_model/validations/validates.rb:79.

Any pointers would be really helpful.

Upload attachments to stories

Hi, I just know the project I was working in my free time in another very similar, but this is much more advanced.

Iยดm still studing the code, i will try add thee feature to upload attachments.
Do you have preference over some plugin?

Thanks.

Installation w/ rake db:seed

On a brand new rvm'd install I get this error when running rake db:seed:

rake aborted!
Validation failed: Email has already been taken

Can't see new stories

I've just downloaded, run, logged in as the test user, created a new project, added a new story and the story doesn't appear (it's being written into the database though). Wondering if this is a known issue...

also is there a google group (or similar) for fulcrum

Making fulcrum Jruby compatible

Fixing the Gem file. (I want to claim this so please let me figure how to do the git hub thing).

remove this line: gem 'sqlite3'
add this:
platforms :jruby do
gem 'activerecord-jdbc-adapter', :require => false
end

group :development, :test do
platforms :jruby do
gem 'jdbc-sqlite3', :require => false
end
platforms :ruby do
gem 'sqlite3-ruby', :require => 'sqlite3'
end
end

An admin interface would be nice...

In order to be able to do admin admin stuff such as

  • Remove signup page
  • Control your projects and users
  • authenticate through different means
  • include logos of your company
  • change the e-mail from and links from there and not from the initializers

Lost data creating new stories

These are the steps to replicate the problem:

  1. You create a new story (chilly bin) and input some fields, do not save it yet
  2. Moves another story in the same container (i.e. chilly bin --> backlog)
  3. The story you created but not yet saved moves to the beggining of the chilly bin, but all the content you created is lost :/

License in plain english

I've tried reading the license, and many projects use AGPL with different restrictions. However, it'd be great for future contributors/users if they could find out answers to the below questions:

  1. Can I make modifications by forking it as a public repository?
  2. Can I distribute my changes to other users?
  3. Can I deploy this app on my own servers and use it for my own company's purposes?

Thanks

Accepting/Rejecting more than one story will make the other stories to disappear

I've got Fulcrum successfully running on a production environment but there's a bug as described in the title.
The steps to reproduce it are:

  1. Add a couple new stories (two or more). Estimate, assign and do whatever you find fancy when creating it.
  2. Start the story.
  3. Finish the story.
  4. Deliver the story.
    (Follow these steps the number of times you created stories. I tested with 6).
  5. Accept/Reject one story and watch it to mark as Done and moved to the Done panel/box.
  6. Accept/Reject another story and watch how them all disappear magically.
  7. Refresh the page to make your stories to resurrect from the ashes.
    If you follow these steps, you will be able to reproduce the error. Also, after you refresh the page to see again your stories, you'll notice that they are not in the Done panel but in the In progress one, even though they have already been marked as Done/Rejected.

Any ideas on what could it be?

Javascript files fail to parse in Safari

Environment:

Server: OSX 10.6.7
Ruby: 1.8.7-p334 (rvm)
DB: sqlite 
I cloned the code, ran rake db:migrate db:seed followed by rails server

Client: Safari 5.04 (6533.20.27)

Steps to reproduce

1. clone code
2. run bundle install
3. rake db:migrate db:seed
4. rails server
5. go to http://localhost:3000
6. log in as [email protected]/testpass
7. Click the Test Project show link

Expected Result:
The app would show the Test Project UI

Actual Result:
The app shows an empty Project UI and the console contains the js error described
In fact the parse errors occurred when loading the js in step 5.

Safari console looks approximately like this:

SyntaxError: Parse error      story_view.js:222
SyntaxError: Parse error      app_view.js:73
[]                                               app_view.js:14
ReferenceError: Can't find variable: StoryView

For FormView at least, JSLint reports this problem for:

Problem at line 6 character 32: Expected an identifier and instead saw 'for' (a reserved word).
return this.make('label', {for: elem_id}, value);

Unable to move stories around

Perhaps I set this up wrong somehow but I have attempted to install Fulcrum a few times now over the last few months and everything works great except I cannot reliably move stories around, which is arguably the core feature of Fulcrum. Right now I am unable to move anything from the ice box to the back log using both Chrome and Firefox. Previously, I was able to move stories around but about 10% of the time, it would place the story at a different location than expected.

Markdown syntax support for free text fields

As a user
I should be able to enter notes and descriptions about my story in Markdown syntax
Such that I can have clearly readable output when I hover over the story tooltip & when looking at the plain text.

Plz?

Uncaught RangeError: Invalid array length (underscore.js:416)

Steps to recreate:

  • follow setup instructions in readme
  • login as test user
  • create new story with 'state: accepted'

All stories disappear, and reappear when the page is refreshed.

Browser: Chrome 14.0.835.186 on OS X

Same behavior in Safari 5.1 (7534.48.3) but the error is 'RangeError: Array size is not a small enough positive integer.' and Firefox 6.0.2 error is 'Error: invalid array length'

Chrome screenshot

Allow custom domains in action_mailer host name

Issue #10 had a fix to get the APP_NAME from the ENV, but this won't help for installatons on heroku (or elsewhere) using a custom domain. I propose to add an APP_HOST setting which would override the APP_NAME.heroku.com if present.

NOTE: Since fulcrum now requires Cedar stack on heroku the host should be APP_NAME.herokuapp.com as well.

Story search

I'm adding story search to projects, like Pivotal Tracker.

GET "http://0.0.0.0:3000/projects/1/stories/search/something to search"

{
  "total_hits_with_done": 1,
  "total_points_completed": 5,
  "total_points": 6,
  "total_hits": 5,
  "stories": [
    {
      "id": 1
    },
    {
      "id": 2
    },
    {
      "id": 3
    },
    {
      "id": 4
    },
    {
      "id": 5
    }
  ]
}

The JSON is the same format as PT. (I assume 'total_hits_with_done' and 'total_points_completed' means stories with state set to finished.)

Sound good?

No backlog

Hi,

I use the last version of fulcrum with Ruby 1.9.3 and rails 3.2.8

Given I created a story with state : unstarted
when a save this story
Then the story move in the column "in progress"

But, your code indicate : "scope :backlog, where(:state => :unstarted)"

My backlog is alway empty, I can't move stories into the backlog

I have no log which indicates the problem

Best regards
Yannick

Registration could not be performed

Hello.

I tried to register on my fulcrum setup. Confirmation email arrives, but the activation link is broken.

Is this already fixed or noted?

Miha

Can't launch rails server because of FasterCSV

Cloned the repo, bundled, tried to start rails server, got this message:

Please switch to Ruby 1.9's standard CSV library.  It's FasterCSV plus
support for Ruby 1.9's m17n encoding engine.

Looked around and I found nothing indicated what this means, I installed the fastercsv gem as a last try. No effect.
Ideas?

Compass/SCSS

Hi,

Great project you have there, Malcolm! As a designer I'm really thinking of contributing some aesthetic improvements. Would you consider adding Compass to the project so the stylesheets can be cleaner? That would be:

$ compass init rails .

...and renaming the CSS files to app/stylesheets/fulcrum.scss. I suppose this is entirely optional, but it would make things neater (CSS3 features with just @include border-radius without vendor prefixes, yay!) and perhaps would entice other designers to help too.

removed Array#enum_with_index from 1.9.x ruby

method Array#enum_with_index was removed from ruby 1.9.x

Started GET "/projects/new" for 127.0.0.1 at 2011-08-20 14:34:23 +0300
  Processing by ProjectsController#new as HTML
  User Load (0.8ms)  SELECT "users".* FROM "users" WHERE "users"."id" = 1 LIMIT 1
Rendered projects/_form.html.erb (101.3ms)
Rendered projects/new.html.erb within layouts/application (102.8ms)
Completed 500 Internal Server Error in 197ms

ActionView::Template::Error (undefined method `enum_with_index' for #<Array:0x934b148>):
    27:     </div>
    28:     <div class="field">
    29:       <%= f.label :iteration_start_day %><br />
    30:       <%= f.select :iteration_start_day, day_name_options %>
    31:     </div>
    32:     <div class="field">
    33:       <%= f.label :iteration_length %><br />
  app/helpers/projects_helper.rb:21:in `day_name_options'
  app/views/projects/_form.html.erb:30:in `block in _app_views_projects__form_html_erb__28841374_90889460__174918754'
  app/views/projects/_form.html.erb:1:in `_app_views_projects__form_html_erb__28841374_90889460__174918754'
  app/views/projects/new.html.erb:5:in `_app_views_projects_new_html_erb___562340129__624859708_461882293'
  app/controllers/projects_controller.rb:31:in `new'

Highlight effect on stories updated by another user not working

When we log in and update a story from another browser, the updates are fetched on the first browser but we do not see a highlight effect on the affected story. The code appears to be there for it but it doesn't seem to be running or is not having an effect. We cloned the master (not our fork) and found the same behavior.

We are investigating.

Jasmine Test failure on Safari - Invalid Date

Environment:

Server: OSX 10.6.7
Ruby: 1.8.7-p334 (rvm)
DB: sqlite 

Client: Safari 5.04 (6533.20.27)

I ran the jasmine test suite and it failed for 2 tests

Project model
  should get the right iteration number for a given date
    Expected NaN to equal 1.
    Expected NaN to equal 2.
    Expected NaN to equal 1.

  should return the start date
    Expected Date(Invalid Date) to equal Date(Invalid Date).
    Expected Date(Invalid Date) to equal Date(Invalid Date).
    Expected Date(Invalid Date) to equal Date(Invalid Date).

When I create a new Project, its start_date is set to, for example, '2011-08-22'
And new Date('2011-08-22'') yields Invalid Date in Safari

`rake db:seed` is trying to send a confirmation email in development env

Reported by Fabio Santos and others:

root@ubuntu:/var/www/fulcrum# bundle exec rake db:setup --trace
** Invoke db:setup (first_time)
** Invoke db:create (first_time)
** Invoke db:load_config (first_time)
** Invoke rails_env (first_time)
** Execute rails_env
** Execute db:load_config
** Execute db:create
db/production.sqlite3 already exists
** Invoke db:schema:load (first_time)
** Invoke environment (first_time)
** Execute environment
** Execute db:schema:load
-- create_table("changesets", {:force=>true})
   -> 0.0100s
-- create_table("projects", {:force=>true})
   -> 0.0189s
-- create_table("projects_users", {:id=>false, :force=>true})
   -> 0.0172s
-- create_table("stories", {:force=>true})
   -> 0.0157s
-- create_table("users", {:force=>true})
   -> 0.0287s
-- add_index("users", ["confirmation_token"],
{:name=>"index_users_on_confirmation_token", :unique=>true})
   -> 0.0032s
-- add_index("users", ["email"],
{:name=>"index_users_on_email", :unique=>true})
   -> 0.0033s
-- add_index("users", ["reset_password_token"],
{:name=>"index_users_on_reset_password_token", :unique=>true})
   -> 0.0044s
-- initialize_schema_migrations_table()
   -> 0.0074s
-- assume_migrated_upto_version(20110706094137, "db/migrate")
   -> 0.0187s
** Invoke db:seed (first_time)
** Invoke db:abort_if_pending_migrations (first_time)
** Invoke environment
** Execute db:abort_if_pending_migrations
** Execute db:seed
rake aborted!
Connection refused - connect(2)
/usr/lib/ruby/1.9.1/net/smtp.rb:551:in `initialize'
/usr/lib/ruby/1.9.1/net/smtp.rb:551:in `open'
/usr/lib/ruby/1.9.1/net/smtp.rb:551:in `block in do_start'
/usr/lib/ruby/1.9.1/timeout.rb:57:in `timeout'
/usr/lib/ruby/1.9.1/timeout.rb:87:in `timeout'
/usr/lib/ruby/1.9.1/net/smtp.rb:551:in `do_start'
/usr/lib/ruby/1.9.1/net/smtp.rb:525:in `start'
/var/lib/gems/1.9.1/gems/mail-2.2.19/lib/mail/network/delivery_methods/
smtp.rb:128:in `deliver!'
/var/lib/gems/1.9.1/gems/mail-2.2.19/lib/mail/message.rb:1989:in
`do_delivery'
/var/lib/gems/1.9.1/gems/mail-2.2.19/lib/mail/message.rb:230:in `block
in deliver'
/var/lib/gems/1.9.1/gems/actionmailer-3.0.9/lib/action_mailer/base.rb:
426:in `block in deliver_mail'
/var/lib/gems/1.9.1/gems/activesupport-3.0.9/lib/active_support/
notifications.rb:52:in `block in instrument'
/var/lib/gems/1.9.1/gems/activesupport-3.0.9/lib/active_support/
notifications/instrumenter.rb:21:in `instrument'
/var/lib/gems/1.9.1/gems/activesupport-3.0.9/lib/active_support/
notifications.rb:52:in `instrument'
/var/lib/gems/1.9.1/gems/actionmailer-3.0.9/lib/action_mailer/base.rb:
424:in `deliver_mail'
/var/lib/gems/1.9.1/gems/mail-2.2.19/lib/mail/message.rb:230:in
`deliver'
/var/lib/gems/1.9.1/gems/devise-1.2.1/lib/devise/models/confirmable.rb:
50:in `send_confirmation_instructions'
/var/lib/gems/1.9.1/gems/activesupport-3.0.9/lib/active_support/
callbacks.rb:423:in `_run_create_callbacks'
/var/lib/gems/1.9.1/gems/activerecord-3.0.9/lib/active_record/
callbacks.rb:277:in `create'
/var/lib/gems/1.9.1/gems/activerecord-3.0.9/lib/active_record/
persistence.rb:250:in `create_or_update'
/var/lib/gems/1.9.1/gems/activerecord-3.0.9/lib/active_record/
callbacks.rb:273:in `block in create_or_update'
/var/lib/gems/1.9.1/gems/activesupport-3.0.9/lib/active_support/
callbacks.rb:424:in `_run_save_callbacks'
/var/lib/gems/1.9.1/gems/activerecord-3.0.9/lib/active_record/
callbacks.rb:273:in `create_or_update'
/var/lib/gems/1.9.1/gems/activerecord-3.0.9/lib/active_record/
persistence.rb:60:in `save!'
/var/lib/gems/1.9.1/gems/activerecord-3.0.9/lib/active_record/
validations.rb:49:in `save!'
/var/lib/gems/1.9.1/gems/activerecord-3.0.9/lib/active_record/
attribute_methods/dirty.rb:30:in `save!'
/var/lib/gems/1.9.1/gems/activerecord-3.0.9/lib/active_record/
transactions.rb:245:in `block in save!'
/var/lib/gems/1.9.1/gems/activerecord-3.0.9/lib/active_record/
transactions.rb:292:in `block in with_transaction_returning_status'
/var/lib/gems/1.9.1/gems/activerecord-3.0.9/lib/active_record/
connection_adapters/abstract/database_statements.rb:139:in
`transaction'
/var/lib/gems/1.9.1/gems/activerecord-3.0.9/lib/active_record/
transactions.rb:207:in `transaction'
/var/lib/gems/1.9.1/gems/activerecord-3.0.9/lib/active_record/
transactions.rb:290:in `with_transaction_returning_status'
/var/lib/gems/1.9.1/gems/activerecord-3.0.9/lib/active_record/
transactions.rb:245:in `save!'
/var/lib/gems/1.9.1/gems/activerecord-3.0.9/lib/active_record/
validations.rb:34:in `create!'
/var/www/fulcrum/db/seeds.rb:3:in `<top (required)>'
/var/lib/gems/1.9.1/gems/activesupport-3.0.9/lib/active_support/
dependencies.rb:235:in `load'
/var/lib/gems/1.9.1/gems/activesupport-3.0.9/lib/active_support/
dependencies.rb:235:in `block in load'
/var/lib/gems/1.9.1/gems/activesupport-3.0.9/lib/active_support/
dependencies.rb:227:in `load_dependency'
/var/lib/gems/1.9.1/gems/activesupport-3.0.9/lib/active_support/
dependencies.rb:235:in `load'
/var/lib/gems/1.9.1/gems/activerecord-3.0.9/lib/active_record/railties/
databases.rake:281:in `block (2 levels) in <top (required)>'
/var/lib/gems/1.9.1/gems/rake-0.9.2/lib/rake/task.rb:205:in `call'
/var/lib/gems/1.9.1/gems/rake-0.9.2/lib/rake/task.rb:205:in `block in
execute'
/var/lib/gems/1.9.1/gems/rake-0.9.2/lib/rake/task.rb:200:in `each'
/var/lib/gems/1.9.1/gems/rake-0.9.2/lib/rake/task.rb:200:in `execute'
/var/lib/gems/1.9.1/gems/rake-0.9.2/lib/rake/task.rb:158:in `block in
invoke_with_call_chain'
/usr/lib/ruby/1.9.1/monitor.rb:201:in `mon_synchronize'
/var/lib/gems/1.9.1/gems/rake-0.9.2/lib/rake/task.rb:151:in
`invoke_with_call_chain'
/var/lib/gems/1.9.1/gems/rake-0.9.2/lib/rake/task.rb:176:in `block in
invoke_prerequisites'
/var/lib/gems/1.9.1/gems/rake-0.9.2/lib/rake/task.rb:174:in `each'
/var/lib/gems/1.9.1/gems/rake-0.9.2/lib/rake/task.rb:174:in
`invoke_prerequisites'
/var/lib/gems/1.9.1/gems/rake-0.9.2/lib/rake/task.rb:157:in `block in
invoke_with_call_chain'
/usr/lib/ruby/1.9.1/monitor.rb:201:in `mon_synchronize'
/var/lib/gems/1.9.1/gems/rake-0.9.2/lib/rake/task.rb:151:in
`invoke_with_call_chain'
/var/lib/gems/1.9.1/gems/rake-0.9.2/lib/rake/task.rb:144:in `invoke'
/var/lib/gems/1.9.1/gems/rake-0.9.2/lib/rake/application.rb:112:in
`invoke_task'
/var/lib/gems/1.9.1/gems/rake-0.9.2/lib/rake/application.rb:90:in
`block (2 levels) in top_level'
/var/lib/gems/1.9.1/gems/rake-0.9.2/lib/rake/application.rb:90:in
`each'
/var/lib/gems/1.9.1/gems/rake-0.9.2/lib/rake/application.rb:90:in
`block in top_level'
/var/lib/gems/1.9.1/gems/rake-0.9.2/lib/rake/application.rb:129:in
`standard_exception_handling'
/var/lib/gems/1.9.1/gems/rake-0.9.2/lib/rake/application.rb:84:in
`top_level'
/var/lib/gems/1.9.1/gems/rake-0.9.2/lib/rake/application.rb:62:in
`block in run'
/var/lib/gems/1.9.1/gems/rake-0.9.2/lib/rake/application.rb:129:in
`standard_exception_handling'
/var/lib/gems/1.9.1/gems/rake-0.9.2/lib/rake/application.rb:59:in
`run'
/var/lib/gems/1.9.1/gems/rake-0.9.2/bin/rake:32:in `<top (required)>'
/var/lib/gems/1.9.1/bin/rake:19:in `load'
/var/lib/gems/1.9.1/bin/rake:19:in `<main>'
Tasks: TOP => db:setup => db:seed

Can not add new story

Hello I just installed Fulcrum. I am really excited about it! Nice design and everything I need at the moment. I created new project just fine. Then tried to add new story and as I click Save button, buttons turns gray and nothing happens. Is this known issue or It's something at my end?

Regards, Miha

"Unable to import CSV" expecting "on" but got "in"

Sass::Compiler#on_updating_stylesheet callback is deprecated and will be removed in a future release. Use Sass::Compiler#on_updated_stylesheet instead, which is run after stylesheet compilation.
Run options:

Running tests:

....................................................................................

Finished tests in 16.031075s, 5.2398 tests/s, 9.5440 assertions/s.

84 tests, 153 assertions, 0 failures, 0 errors, 0 skips
Sass::Compiler#on_updating_stylesheet callback is deprecated and will be removed in a future release. Use Sass::Compiler#on_updated_stylesheet instead, which is run after stylesheet compilation.
Run options:

Running tests:

.....................................F..................

Finished tests in 16.573250s, 3.3789 tests/s, 16.2310 assertions/s.

  1. Failure:
    test_should_gracefully_fail_to_import_an_illegal_csv(StoriesControllerTest) [/Users/whitemac/source/fulcrum/test/functional/stories_controller_test.rb:197]:
    <"Unable to import CSV: Illegal quoting on line 1."> expected but was
    <"Unable to import CSV: Illegal quoting in line 1.">.

56 tests, 269 assertions, 1 failures, 0 errors, 0 skips
Errors running test:functionals!

Add Impediment feature

As tasks are owned and in process it would be good to label them as stopped and create an impediment. I'm kinda fuzzy on how it should be implemented.

Jasmine test "should return a readable create_at" returns wrong time

Show passed skipped
run all177 specs, 1 failure in 1.129sFinished at Thu Dec 22 2011 16:28:55 GMT-0500 (EST)
runStory model
runusers
run should return a readable created_at
Expected '18 Sep 2011, 10:25pm' to be '19 Sep 2011, 2:25pm'.
Error: Expected '18 Sep 2011, 10:25pm' to be '19 Sep 2011, 2:25pm'.
at new (http://localhost:8888/**JASMINE_ROOT**/jasmine.js:102:32)
at [object Object].toBe (http://localhost:8888/**JASMINE_ROOT**/jasmine.js:1171:29)
at [object Object]. (http://localhost:8888/**spec**/models/story.spec.js:256:39)
at [object Object].execute (http://localhost:8888/**JASMINE_ROOT**/jasmine.js:1001:15)
at [object Object].next_ (http://localhost:8888/**JASMINE_ROOT**/jasmine.js:1790:31)
at [object Object].start (http://localhost:8888/**JASMINE_ROOT**/jasmine.js:1743:8)
at [object Object].execute (http://localhost:8888/**JASMINE_ROOT**/jasmine.js:2070:14)
at [object Object].next_ (http://localhost:8888/**JASMINE_ROOT**/jasmine.js:1790:31)
at [object Object].start (http://localhost:8888/**JASMINE_ROOT**/jasmine.js:1743:8)
at [object Object].execute (http://localhost:8888/**JASMINE_ROOT**/jasmine.js:2215:14)

Stories do not display in Firefox 7

Testing on Ubuntu 11.10, Firefox 7.0.1. Jasmine suite runs fine, but projects#show errors with:

'end iteration number must be greater than start iteration number' when calling method: [nsIDOMEventListener::handleEvent]

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.