If there were an API to ping each time a build runs (which would need to be branch-aware) to say which features/scenarios ran, and passed/failed/pending, and then gave a little spark-line per feature & scenario, that would be really nice.

Aggregating that information onto a dashboard would _also_ be really nice.

I've a cucumber project that has some features 2 folders deep. It would be good to see my folder structure represented in Relish instead of just showing the single folder.

Since one of the goals of Cucumber is to share features within your organization, a nice print stylesheet that minimizes navigation and branding elements would be awesome. Perhaps that's a paid feature?

This was @tooky's idea: add an RSS feed for a project so you can see when new features are pushed.

Have little +/- buttons on the title bar of each scenario so they can be collapsed, thereby allowing me to see an overview of the feature.

I'd like to be able to change the email address associated with my account, for example if I change companies.

It would be great to view the features in plan text, too.

Relish needs to charge a small subscription to be self-sustaining.

The current plan is to charge for private projects, so public projects would remain free.

If you think Relish is already worth paying for, please vote for this suggestion.

If you don't think Relish is worth paying for yet, please suggest or vote for the other features on this forum that you think it still needs before we launch.

Within our features folder we have a number of folders with different components. At the moment the only way I can get the features to push through Relish is to rename one of the components to 'features'. Then run relish push. I want to explicitly tell Relish which folder to push the features from.

For example:

relish push features/cucumber/web_ui ...

When you read a scenario outline with a tables of examples, your eyes need to continually switch between the outline and the examples. It would be quite neat if you could hover over a row from the examples, and see the tokens replaced by actual values from the table.

Lanyrd leverages Twitter's social graph. Could Relish leverage Github's organisation graph to map to it's own roles and rights system ?

There's a sometimes tension between creating useful test cases and useful documentation. I think it would be useful to be able to hide some scenarios, or even whole features from being published.

You should be able to navigate back to the project page (with the readme.md file) when browsing a feature file. I cannot find anything on the page to take me back their.

I don't actually maintain a public set of features (yet), and I found out about the site via a link to rspec documentation, which made me wonder what else was available to read on the site.

I'd like to be able to search and browse content cross-project.

While I'm waiting for features to be imported it would be nice to know that something is going on in the background. For example some of the feature links failed, but after a little wait they work. So they where still getting imported.

It should be possible to invite people from the organizations page, so that these persons would be added as members of the organization after they signed up.

Add a "Help" link to the web site going to http://relishapp.com/relish/relish