Evan Light

"Bugs" in Tracker pull incorrectly

4

A Bug, when pulled from Tracker, generates Gherkin with "Bug" where it should have "Feature". This causes Gherkin to error. Workaround is simple.

When pushing a feature back to Tracker for a Tracker Bug, pickler outputs "Stories in the started state must be estimated." to stdout". Pickler probably just needs to support logic...

nt

``` Scenario "Query with no query args returns all locations" do given_a_person given_im_logged_in_as :person And "A job with a maximum of zero agents" end ``` 1) Error: test_query_with_no_query_args_returns_all_locations(Geographic_queries): ArgumentError: wrong...

Improved error reporting in stacktrace

3

**Is your feature request related to a problem? Please describe.** When an error occurs within Dataview, particularly DataviewJS, the provided stacktrace often does not indicate a useful location or nature...

Useful error stacktraces

3

**Is your feature request related to a problem? Please describe.** debugging templates is painful due to stacktraces never indicating the file resulting in the error. Nested templates are particularly challenging...

Form submission doesn't have desired behavior

1

Submitting a form within holygrail does not cause the subsequent page to be loaded into Johnson. See http://gist.github.com/364103.

0.6 only works as a plugin

2

/lib/holygrail.rb does not load init.rb As such, 0.6 only works as a plugin. This presumably could be mitigated by requiring init.rb at the bottom of lib/holygrail.rb

The current behavior makes regex entry more error prone as the field keeps trying to complete a tag. Thanks! LOVE this plugin.