Hacker News new | past | comments | ask | show | jobs | submit login

We've just spent a good half hour or so trying this out.

It has a snappy interface but in some respects it's very heavy - ie in the number of clicks needed to do anything.

The main one for us is estimating. We want to be able to go through a list of stories and edit the estimates. The fact that the table of stories isn't editable means we have to open up the dialog for each story to edit the estimate.

As a comparison, we're currently using Airtable for some projects and Notion for others. In both of those, you can do that.

Also the ability to add our own fields to stories is something we use quite a bit.

Otherwise it's pretty nice.




(Co-founder here)

Great feedback, thank you! We do have bulk editing (to update many stories at once to the same value) and an ability to update properties in Epics table views, but not Story table views. Your use case makes total sense. We’ll add your feedback to our internal Story for this feature, and if you’d like, we’d be happy to let you know if this ends up being built.


Please notify me when this goes live, moving from Clickup to Clubhouse btw, liking it so far.


Sure. Would definitely be willing to give it another try at some point.


One of our frustrations with Jira is that estimates are only editable in your backlog or active sprint. We often open stories in different tabs, and constantly have to switch back to the backlog in order to add/update the estimate.

I can't believe why nobody has implemented in both screens.


The in the tool we are building (https://linear.app), you can just hit shift+e to estimate in backlog/active/sprint and in the issue view. (https://cl.ly/81b9a29734dd)

You can actually do all actions for the issue just using the keyboard on any list/board view or issue view.


Have you added the field to the issue screen? By default it's not there, and if there's no points, it won't show unless you click the edit button. But I use Jira and can edit estimates on the issue screen




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: