In T5024#59425, @epriestley wrote:

For the first case, maybe a column permalink would be a better solution? Then you could navigate back up the board easily. We can structure this as a search query instead (and it might not be bad to make that possible, for Dashboard panels) but it will lose some context. There's also no control which will easily let you select a column right now, and building a nice one is probably a fair bit of work (plus, it overlaps a lot with some other less well-defined tasks and infrastructure-blocked things).

thanks! Will try it out when we update here. @angie can you ping me once we update to this version on our side?

sweet. I am sure we can work with those. I think Herald Actions in itself should work pretty easily in our existing workflow. I am very excited about server-side lint, but a bit more documentation about them would help me out. I can't understand it fully with your comments :)

duhh yes .. sorry!

btw, it seems the extension comments every time there is an update to the diff instead of just the first time. That is a bit annoying: was this expected? is there a quick fix to it?

also, sorry. I should have been more clear.

aargh.. ok. shouldn't be a big deal though; I am pretty sure we will pay. The hard part is not the budget.

awesome! thanks! you weren't kidding about 15mins :)

cool! thanks!

I am interested in getting an estimate

This might be an easier thing to prioritze and pay for (even as an extension). Is there a way to get an estimate?

@chad I figured this would be a simpler and less disruptive task, so filed it separately. The other task still doesn't have any consensus on whether we want to do something and if then what. I was hoping this could get faster consensus.

good point. Unfortunately, the mailing list is already set up and migrating that might be more effort than needed (there are all the existing links; subscribers; guidelines etc).

Sorry, that was badly phrased. My apologies.

this works. The only problem is that every response will create a new task. I can hack around it, I think, but was wondering if there was a way to tell Phabricator to not create a task in those cases.

ohh cool! yeah .. let me try this out. thanks @chad

I agree. This can't be the long term result of the UI.

Sorry, I didn't create this task so I have no idea about whats happening here much. The actual concrete tasks were discussed in the one on one with Phacility.

hey! So I am in the security team at Dropbox. Would you have time to chat with some of us when you are at Dropbox next week? A lot of this might be easiest to figure out IRL.