I plan to let you choose a custom field to serve as "points" instead of counting each task as 1 point, but this isn't a priority.

In T4427#70957, @epriestley wrote:

I started implementing like half of this, but realized we need to update the counts when you move stuff between columns.

Sooo yeahhh...

At least from my testing.

This isn't a CSS issue, it should display fine. We're just not triggering the js to show the indicator.

For summing things see T4427

One thing I was missing from Mingle and would be happy to see here is to assign CSS style changes to certain field values, e.g. have a "blocked" or a "taken" field and dim the card if it is set. (An alternative functionality to represent the same meaning in Mingle was rows, but as I understand Phabricator boards won't have that.)

In T4863#80491, @qgil wrote:

The mockup in the description shows story points, and we have at least one team currently using Mingle that relies on story points being visible in workboards.

The mockup in the description shows story points, and we have at least one team currently using Mingle that relies on story points being visible in workboards. How difficult would it be to implement just that part? For what is worth, we are planning to use the Burndown extension, and I wonder if an interim solution would be to introduce this feature through that extension.

I would definitely have a use to display additional projects a card belong to (was T5356).

For any users who have extra backlog columns... to clean them up, make sure there are no tasks in them on the web ui and make sure you check for completed tasks too...! Visit the project homepage and look at the "flag for later" URI - the project PHID is in it - and save this phid for later. Visit the workboard and "edit" the backlog column that gets to live and note that ID for later too.

That patch would be out of my league.

@chad - unless you have plans on a migration, I think we can close this out. I removed the support impact project since this is no longer generating support.

Passing along a trigger-like request: Have a commit message like ReadyForQuality T123 move a task to the 'Ready For QA' column in the appropriate (magical? configured?) boards.

It would also be be nice if one could map a field with S/M/L/XL into points for the purpose of the sum. Or at least if that was possible if you wrote your own custom field class.

D10651 will at least prevent future issues, will have to follow up if a migration is possible.

Requested at Wikimedia as well: https://phabricator.wikimedia.org/T555

T5793: Add support for personal workboards

In T4890#56097, @chad wrote:

Additional Board Types like "Personal", where I can move my tasks to how they relate to me personally. As in, stuff Im working on now, upcoming, backlog.

Also, probably should be in a separate task, but the ability to outright delete a column/list would be useful, especially since active tasks can exist in hidden columns which is very confusing.

also, if we can get a procedure for removing 'backlog' lists created due to this bug, it'd be a real help. I have one board that currently has eight backlog columns :(

Support Impact This breaks boards in a confusing/surprising way and @tcook hit it in the wild (but I don't think developed repro steps).

Support Impact This behavior is surprising and buggy.

I'll poke at CSS

Yes per board with that possibly being a thing that changed fairly often ( so I suppose something that acted like the sort/filter buttons in the top right would be idea).

You can set the color, priority, and label in Maniphest Config already, but it sounds like you'd maybe want to change that meaning on a per project basis?

Internal request has been to be able to control what the color on ticket means. For example, if we have a type field, to make the stories different from the bugs or maybe to make the 't-shirt-size:XXL' tickets different from 't-shirt-size:S'. This is mostly for planning purposes (like during a sprint planning meeting) and not something we would want to set globally for any context a ticket is viewed in.

thx, T4863: Allow Workboard Cards to be customized for display would do the trick if blocking and blocked task id caould be added as a custom field to cards.

Going to merge it over so we'll have this information on that ticket.

The personal workboards is the more interesting task, it would independent and let you organize just your work without disrupting a Project's board.

It's an interesting idea, but it has issues since we'd no longer have a single vision of a board or column. We generally expect Dashboards do the heavy lifting when it comes to providing you with your view of your workload. Additional tasks that might interest you:

To followup from IRC: If the single page view had the 'Batch Task Editor', I think between this and T5474 would cover > 90% of the internal feedback I've gotten.

We don't default focus forms on normal pages. We haven't seen other requests for this behavior, and it would interact poorly keyboard shortcuts.

I think this is worth fixing separately.

Yeah, let's track this separate.

We don't currently rebuild the entire board. @epriestley curious on your thoughts, if better to wait for realtime everything or maybe a workaround is simple enough.

Happy to see this fixed as part of T4900 but note that it affected for a single user in a single tab which may or may not be different in a way that matters.

Oh, thanks :) FWIW, yes, we just upgraded to the latest version before I created this task.

Nevermind, this is known and being tracked.

Is your install up to date?

I'd agree we should have a one-click add task. we'll look into adding it back somewhere.

@epriestley is there a better way to bulk add tasks than using the Workboard UI, because that is when the action became frustrating, maybe a link in the drop-down to bulk add would help if it exists?

We haven't seen other reports of users having difficulty finding this functionality, and it now says "New Task" explicitly instead of being sort of a mystery meat "+" icon. Even if this change is worse for discovery on the balance, I don't think it has made a very large impact either way. In this case, you found the interaction, even if it wasn't where you expected it to be.

@epriestley in the discussion it was never really resolved as to why 2 clicks is better that 1 click. As a user who was batch adding a number of tasks this was frustrating to click twice.

See D10190 for discussion. The change was intentional.

Yeah I think there may be a UI regression, in that we did have a + in the header to quick add a task. I cc'd @epriestley to see if he remembers.

I got some some similar feedback which I would summarize as "reduce
number of actions needed to create a new task".

I may be misunderstanding your request. Is it that you want empty columns to have a create link or all columns to have a create link.

I respectfully disagree with your decision because consistency and an Intuitive user interface are not the same thing. I'm finding in a lot of case the one size fits all approach to UI on Phabricator can get a little verbose.

The concern here is that some links are accessible and some are not. We'd prefer to stick with the consistent dropdown for the time being, but we may look into it again if we decide to build fixed height columns.

Fullscreen mode should be handled natively by your browser (like Chrome). Font size, same thing, your browser can control this. As far as removing the navbar, we used to have a showChrome parameter you could pass to the URL to remove it, but I think it's broken. I can fix that.

That seems to have fixed the issue nicely. Thanks a lot :)

Let me know if you're still seeing issues after that, this drag-and-drop stuff is a bit finicky.

Closed by commit rPf02aed10e769.

◀ Merged tasks: T6051.

No worries, just glad you've been able to reproduce it and I wasn't going
mad!