How many tasks are you attempting to batch edit?

(Specifically, the scrolling is a feature which I added in D10188 but punted on making work in Firefox.)

@epriestley this is already a vast improvement, thanx for {D15093}.

I think we can do the background drag thing too, that shouldn't interact poorly with anything else (I think? Probably?).

We're probably going to do per column scrolling, or at least see how it feels in testing. Will have to see where we end up.

In a semi-related topic, I find myself constantly expecting Trello-style behavior where a user can click + drag outside of cards to scroll vertically/horizontally.

After D15093, this should be a little better:

Pass with points and faces.

Some of the Pholio stuff is motivated by thinking about v2 sometime down the road. Like having a "workboard" view of my designs and their status could be handy (shipped, needs more work, planned).

Points look great.

Blocking is T5353
Mock is roughly T9520
Diff ... can't locate the task offhand.

I'd like to put off building customization for as long as possible. I think we'll want it eventually to give custom fields broader support, but we can call all of that part of T418.

@epriestley do you think we need to allow customization? My main thought is if we can keep it simple and clean, users won't likely ask for less options. Though it's easy to checkbox which items you'd want to display.

Oh, yeah we should add points in there too. Whether a task is blocked or has children has come up in other tasks floating around, though for all tasks, not just workboard cards.

FWIW, here's what WMF's customized cards (by the Sprint extension, I think?) currently look like:

My current thinking is just to expand the metadata on the cards for everyone, and not build anything "customizable" until we get a better sense of what the expanded metadata isn't conveying. Most of the viewpoints here seem to strictly be able wanting additional projects. I've take a design pass at adding the following information to cards:

This is expected. Please read Customizing Forms carefully.

But maybe my memory is poor and Workboard cards are more custom than I remember.

It shouldn't require any design, they should just work like they do in Maniphest normally, but without the board's main project. ie, if you're in Differential, and you had Differential and Mobile tagged, just show the mobile tag.

If possible: display both. if not possible - many ways:

I'm happy to send a diff over, but my design skills are quite lacking. How would.you think that the project tagd should be displayed? For example, suppose that a task is tagged with project X, Y and Z and is being viewed as a worknoard card for the board of project X. I'd say that we should show either Y or Z (as X is implied), but I'm not sure which should be preferred.

It should just be the default moving forward, I don't plan to introduce any special settings. Feel free to send a diff over if you like.

Projects displayed on workboard cards. We usually end up doing "[PROJECT] Title" as a workaround.

Probably not. What part do you need specifically, we're already building v3 projects.

Is this available for prioritization?

In T6027#135704, @isfs wrote:

Would it perhaps be simpler if instead of developing a "Change columns" UI, actions can be added to move columns, something more along the lines of what I mocked up for T9280, i.e. a simple action with two parameters, rather than a monster action with parameters for all existing boards?:

If you want to move the task on multiple boards (which I imagine is relatively, if not absolutely rare) you would just add multiple actions. The order of the actions is clear, even if not mutable.

Ah, thanks! I thought we had one of these floating around.

Dup of https://secure.phabricator.com/T6051#75103 ?

I still think the original request is the best solution. Creating save states or visibility filters sounds overly complicated. Why would you not want users to be able to delete columns (other than the axiom that you don't let users delete anything)?

Maybe a better approach would be to let you filter which columns are visible more flexibly. It sounds like all the existing use cases are arising because "hide" isn't being used to archive obsolete columns, but because it's being used to give workboards multiple states where each state has a different set of visible columns.

yeah maybe lazy is bestest

After "thinking carefully" about this I am going to do the lazy / less bold approach and we can sort it out later so you can have this back. :3

Yeah, maybe it's not terrible, will have to see what other feedback we get here is. One idea might be to allow columns to define what forms are there, with all forms by default on the Backlog.

("Not really." in the sense of "I don't have anything in mind" -- I agree that it might feel weird.)

Not really. I was going to do this:

In some regards, having "bug report", et al. on a column might feel weird. Or do you have something in mind?

I'm going to try to bludgeon this in for EditEngine, we can refine it in Projects v3 if I ham it up.

I think D14016 actually fixed this?

I don't plan to implement this. We haven't seen other interest in it and your use case seems fairly unusual.

See Contributing Feature Requests for help writing a feature request.

The column names for a task within a project are accessible through the conduit API with a little work. Here is a gist containing a python script to get the tasks associated with a project and workboard column then print them grouped by status.

In T9718#143261, @chad wrote:

Have you never noticed the nautical patterns in Phabricator?

Have you never noticed the nautical patterns in Phabricator?

Scuttle?

oh.

not that it was implemented.

What about making drop zones ultra long down i.e. to show only names at the top and allow users to drop anywhere, not necessarily at current small "drop zone" at the top?