In T5793#108195, @epriestley wrote:

If anyone does this, I'd be interested in feedback on how it goes.

Yep, thanks. I did just mean point value and the pointers to the new project designs I think solves any questions I might have.

I think I misunderstood and by "size" you just meant "point value". This will happen eventually as part of other projects work (T9378, T3670) but those need to happen first. I'm not yet sure if we're going to make this a first-class value or let you designate a custom field as a "points field" or something else.

Your expectation is that a card worth 10 points is rendered 10 times larger than a card worth 1 point?

It would be great to have this in Maniphest - whatever way there is...

+1 for projects at the very least. If space and clutter is a concern maybe just show the icon and color of the tag (project) - that way we can at least associate different skills involved with tasks and that would solve the problem with lack of lanes for us.

https://secure.phabricator.com/book/phabcontrib/article/feature_requests/#describe-problems has a bit more detail on helping us understand what you're looking for.

We don't really have attachments in Maniphest. Our expectation is that people with either use Pholio (in case of design) or drop images into the description via Remarkup.

I would like to confirm that it would be a great addition to be able to move a task to a different column within the edit mode.
Especially if you're working within the workboard view, it would be efficient to not need to explicitly move the task to another column, right after the task has been edited within the inline popup (or vice versa).

+1 regarding the option of being able to display additional projects on a card within the workboard. (= exactly what @weyrick, @chad, @20after4, @swisspol mentioned earlier)
This would be very valuable for project management purposes.

See Planning, Roadmap, Paid Prioritization.

How is this task going ?

This would be extremely useful for our sprint boards (either a default or stickiness).

I also need to be able to delete columns, not just hide them. I use hidden columns for various archival statuses and occasionally need to actually look at them. Unfortunately, when I turn on hidden columns I also get all the temporary/unneeded columns that I had to hide because I couldn't delete them.

I want to resolve T8588 before pursuing this to make sure the issues aren't conflated, although I think this isn't related.

That would make this function at least useable in some way, even if it would be a bit complicated if a task has several (5+) projects assigned (which is, what you said already, very rare).

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?:

ok thanks.
suddenly wishing batch edit would let me bulk-rename (or at least append) task titles ;)

Renaming the task is likely the easiest workaround until T4863

let's say i have 2 projects "Square" and "Circle"
Square may have a task for "Support C++ 11"
Circle may have a task for "Support C++ 11"
if we use a Sprint project to track commitments for the whole team, in Sprint's workboard view we cannot tell the 2 tasks apart without clicking on them to understand the context of the project they are for.
(or even if they didn't have the same name, we lack context, we may assume that Triangle wants support for C++ 11)

I would find it helpful to filter the manifest query based on project column name

I fooled around with this and @epriestley's fix to no resolution. If you find a fix you are welcome to submit a patch.

@chad, does this mean there is no fix for this?
where is the file that consist of this position: static located at?

Yep that was my main problem with it and really still is even though I am
now using workboards properly. It's just information that isn't needed imo.

Aside from affecting the default view of a project, it also affects individual task pages.

These are already covered by some other tasks. T4316 is commenting when editing a task, T6027 covers moving tasks to new a workboard via the edit interface. Stacking actions is M1430

Yeah, likely just a didRejectResult() issue.

I guess this is related to / a duplicate of T4345.

Every... day...

This was causing a lot of headache to our team, so we simply switched off change of the priority (by @erik.fercak), may be this would help someone too, until the problem is resolved:

I'll work on updating the patch to improve the visual feedback and then arc diff it. Thanks for your willingness to consider it.

I'd be happy to check it out with a diff. One concern is indicating to the user the drop area is larger or at least that a blank area is a valid drop target. JS should be added to detect you're over a valid area to drop, and apply a new CSS class to that column we can toggle on/off.

See also T6502. Our handling of permissions here has changed a couple of times and this should never be greyed out, I think.

Here is my patch. I can arc diff this if needed (though it will take me a little while, since, as you can probably see, I checked out Phabricator using hg-git rather than git itself, so I will have to do some trickery to use arc diff or clone again). It does not include the changes from running ./bin/celerity map.

The main downside being you'll have less visible cards and have to scroll more.

I think we can just make extra projects the default.

Yes, please add a workboard setting to display all projects on card. My previous request above is almost a year old and user demand has not diminished.

At least, I attempted what you suggest with I3, and not much has come of it.

Loud and clear.

I'm thinking many firms (mine included) would pay towards a desired feature, although not the entire dev cost.

Would love this feature as well.

It's not: the column has a name, position, history, configuration (e.g., maximum points), and triggers

no worries! wasn't easy for me to find either

Thank you for merging.
(Looked for relation "mobile" "workboard" but did not find anything related.
This is exactly the required solution, thank you and sorry for the duplicate.)

Since projects are the go-to for labeling tasks, showing projects in workboards sounds like a high value, however, it could look pretty noisy if all projects are shown.

its information content is 0.

I think this bug was unnecessarily morphed into something unrealistically complex. Deletion of workboards would solve most issues and it would be easy to address

it's intentional that users (including administrators) can not permanently destroy data

by setting some limit (default e.g. 0) on the pieces of information one can destroy. If the workboard has all items in a single column, its information content is 0.