Thanks @epriestley

I'll lump that into T10350.

We've been using our own custom points field for a couple years now. Is there/could there be a plan to ease migration to the new formalized points system? (a bin script would be fine).

@mrkanaly I had a similar issue. Putting the following in my .vimrc allows me to type arcl to get the same behavior as the old arc land command:

Really awesome.

I wish I wasn't using JIRA...

Awesome progress; cover images, points, points graph & project cards rectify just about everything I considered Workboards to be lacking.
Nice one

If so, how do I assign something to a member (or whomever) who doesn't yet/right now have a shown task?

That is, this is a valid column:

@epriestley: Yes, I misread the comment and subsequently deleted my response. My apologies.

There's some argument for showing more headers than the actual assignees, so you can assign a task to someone with no tasks currently assigned.

• Cards also show other projects.
• Workboards can go fullscreen.

Commenting to show my interest in such a script. I'd be completely fine if the migration script did what @jdforrester described and merged members of A to B.

It's just Group By Assignee, so of all the tasks on the board, who is doing what, how much work is it, and what is unassigned.

I like this idea. For the "assignee" options, what would the ones shown be?

Haha. I really do think "suggest a profile picture" might turn out to be pretty fun. Maybe I'll kick out that and {button} if I want to take a break before doing callsigns.

@kaldari Most of this ticket is asking for "save priority as the default order" and/or "save 'open tasks' as the default filter" or something similar. Those were implemented by D15260, and are now supported. You can see them in action on this install, and D15260 has a couple of screenshots of the feature.

@epriestley I need to suggest a profile photo to @cburroughs

We have like 50 "Team X Sprint 123" projects that would be nice to turn into "actual" sprints. But they are all old sprints so that's just for my need to keep things looking tidy.

Oh, forgot the implicit equivalent of use-case #3:

In T10350#159113, @epriestley wrote:

@jdforrester, in your situation, how would you want to handle members?

I suppose that typing Points between [2] and [3.9999999999] is probably an acceptable workaround for expressing the range [2, 4) if anyone does come up with a use case that requires exclusive ranges.

Thanks, that's helpful. That's pretty much what I figured, and it's reassuring that no one has come up with "exactly 3, 5, or 11 points" use cases, or use cases that require a mixture of inclusive and exclusive ranges, at least so far.

My tentative plan here is to write a script that does it and make it available in this task. I want to do this a bit on this install too, mostly so we can have better direct exposure to these features ourselves.

My real-world use cases (based on the Phragile extension, before this existed):

• Show me tasks with points explicitly set to zero (external dependencies), so I can chase
• Show me tasks with points set to some value (e.g. ultra-epic), so I can re-cut my roadmap around them
• Show me tasks with points set to more than [X], so I can make sure we do hard tasks earlier [Not met by Phragile, would be nice]
• Show me tasks with points unset so I can estimate them [Not met by Phragile, would be fantastic]

Yeah, why don't you file a separate task for the importer thing. I saw https://phabricator.wikimedia.org/T123078 on WMF recently, too. I think there will probably be enough demand for this to bring something formal upstream, but maybe only a few installs care (or everyone has different weird requirements) and we can just throw a script up somewhere and not have to maintain it.

Registering my interest for being able to move projects into being sub-projects. See https://phabricator.wikimedia.org/project/profile/483/ for an example of using faked sub-projects (with, collectively, thousands of tasks) which I'd love if possible to make "real" without making ten thousand bulk edits, modifying long-dead tasks and melting people's inboxes. Should I file a specific task?

I had to rename all those junk records just so I could hide them after the fact.

Wow. This is awesome. I'm glad you were able to find and trace down this issue with what minimal info I could provide. I'll try to give better descriptions in the future. It would also be nice to remove columns that have no tickets associated with them.

At HEAD:

Yeah, that's the right way; result is a required parameter for unit object.

In T10346#159072, @robertkraig wrote:

they never existed before when I originally imported their workboards

This is now substantially complete.

These are sub projects imported from another project. But they never existed before when I originally imported their workboards. So I was as confused as you to how they suddenly started showing up.

This is now substantially complete.

This is now substantially complete.

Currently, it's hard from me to tell what's going on in the screenshot. Can you give us any more details on the setup?

This mostly applies to if you're following master. stable is only updated once a week.

We expect people to update Phabricator before filing a bug report. We fix bugs very quickly. Even if you just updated a few hours ago, it's helpful for us to not have to spend time hunting down a bug that was already fixed.

I just updated code early in the day, like 2am.

Specifically, what version of Phabricator are you on? There has been a lot of churn on Workboards this week, and even today. Does this bug exist at HEAD?

how did they get added in the 1st place?

Thank you Evan. I found the reason of the issue.
I'm using your batch file to upgrade and when I run it shows the error below.

If you updated two hours ago, you should be ahead of c2502f1, which is about 50 hours old. We've made about 30 changes between c2502f1 and HEAD, which you can see here:

I updated 2 hours ago. And I have just updated.
The issue is still the same.

Update to HEAD. This was fixed by D15232.

I don't think we can guess right for stuff like "Version 6.5" or "Sprint 4/31" without doing a lot of work, since "add 1 to any numbers" won't work in those cases.

2 days is a very long time to import. I'd wait until it's finished (we should still fix the error if we can reproduce it)