Hacker News Reader

Comment by amelius | Hacker News Reader

Does it cooperate with an issue tracker? I.e., is it easy to convert tickets into tasks?

Also, I just watched the demo gif. To move a task from "unstarted" to "started" you have to drag and drop it? Doesn't that get clumsy when the "unstarted" column is really big (which it will probably be in realistic sitations).

View on HN

You can use an integration like Zapier or our API [1] to automatically generate stories based on some external event. As already mentioned you can update the state within the story dialog, or using our GitHub integration you can partially automate the process by setting up rules like so:

- When pull request is opened on master, move story to Ready for Review

- When branch is merged to master, move story to Ready for Deploy

We use these rules ourselves, and they not only reduce process overhead, they make your cycle time data more realistic vs. doing these steps manually.

[1] https://clubhouse.io/api

We don't currently have any official integrations with external issue trackers.

We do have a full API though (https://clubhouse.io/api/) so it probably wouldn't take much effort to build something for your issue tracker of choice, which some of our users have already done.

You can also change the story's state (ie., "started") by going into the story and changing its "State" field.

Don't think it works with an external issue tracker, though I haven't looked closely at the Github integration.

Reply on news.ycombinator.com