I have been trying to see about another way to do this until this is added (if it is I should say). We are finally getting ready to move to Phabricator, and I was hoping there was at least a shortcode or something I can use. Currently what I was trying to do was paste the query URL for a particular project's Passphrase credentials. What we were going to try was getting the query for whichever project's passwords, copying it, and adding it to the Project as a custom link.

Hi @tappers, I can't get your query flow to work on my machine, would it be possible for you to give me a simple example of a working query ?

I second this:

D18836 probably isn't the right solution, however, it's the only straightforward fix I could come up with. I didn't dig into the details of why it 404s when I fix the code in PhabricatorProjectViewController to avoid the fatal. The patch is probably good enough for Wikimedia, however, I'm not sure if it's good enough for upstream.

This seems like a legacy data issue that's probably unique to this install. The only way I could reproduce it locally was:

hi

Doesn't seem to reproduce any more - I have no issue importing from another milestone. Presumed fixed, but if not, please reopen with more detailed reproduction steps.

You can find tasks with no owner by searching for "No Owner", like this:

This is something that is needed every day, e.g. find tickets which are not yet assigned..

Milestones works great for this, but you still have to manually create the workboard (just going into workboard and clicking create - milestones show up).

We do something similar ourselves for technical interviews, but I just related all the tasks by embedding them in the description of a central task:

I think this use case is a reasonable one.

Hello, we used this function (add project to a commit by Herald rule) as well happily for about two years (last update of phabricator was 03/16/2016). The current phabricator update (06/06/2017) now lead to messages in the activity feed in the form of "Herald added a project to rXXXXX: <message>: <project>" and the commit itself (or better the message) does not appear anymore. When we disable the Herald rule the commit-messages appear in the feed again as before and expected.

In T12144#226158, @epriestley wrote:

Why would you want to set those up as milestones instead of subprojects?

It doesn't help that GH/GL Milestones are loose tags with a target date.

We could also let you collapse/expand columns like your mock in T6642. None of this hide/show/filter/collapse/expand stuff is hard -- T11036 and T4900/T10336 are the only really involved JS changes in queue for workboards, I think. It's largely just not clear to me which subset of the proposed tools is most useful, and it feel like major overkill to implement all of them.

But it's mostly moot until T11036 I think. T5024 is vaguely related ("filter to just one column"). T6642 might be related ("save collections of columns") but my recollection is that task was a bit muddy? I haven't re-read it recently.

That's very easy, just a question of whether we want to add the buttons/menu items for it.

Yeah there are some UI tweaks I can do to dissuade accidental milestone creation.

What about workboard filters? View Milestones, View Subprojects? That sounds like a lot of work though. Might be nice on large parents.

One minor fix would maybe be to put "Create Subproject" first on the "Subprojects" page. This is inconsistent anyway -- the tab is called "Subprojects" and the header is "Subprojects and Milestones", but the order in the action column, the curtain panels, and the main panel is "Milestone, Subproject". I think this stuff blame to me in D15152, but "Subproject, Milestone" is probably a better order both for consistency and to gently nudge users toward the more general / less specialized unit of project division.

I don't think this should be a language problem or that "Milestone" should communicate "flexible target" -- physical milestones are big, immovable, evenly-spaced chunks of stone with a single increasing integer chiseled into them. They're a really direct metaphor for the behavior of milestones as implemented in the product. But feel free to send me a diff to swap it to "Iteration" if you think that's clearer, I'm not married to "Milestone".

Maybe it's a language problem. "Milestone" to me says "target" so I think it's a fluid set of targets that may or may not be in an order.

If anything, a hypothetical "Progress" tab should show ALL subprojects and only a SUBSET of milestones: just the last, current, next, and maybe +2 / +3 milestones. If your work is really linear and time ordered the progress of the milestone from five iterations ago isn't relevant most of the time.

That is, milestones largely exist to support future features that depend on a linear ordering, like "push all open tasks to next milestone", automatic creation of the next milestone from typeaheads, automatically scheduling milestones sequentially for charting/reporting, etc. If we let you reorder them most of that stuff sort of goes out the window (or, at least, gets much more complicated). And if these features aren't actually important, I think we could possibly just remove milestones from the product.

There's no technical reason we can't let you reorder milestones, but adding features that let you bind milestones to time ranges may be much more difficult if we let you reorder them.

I'm still ok with allowing people to re-order milestones, hard to imagine we'll get reports asking for it to be restricted.

I think that's conceptually reasonable, but I can't come up with any reason offhand that it should be restricted to milestones instead of showing both milestones and subprojects.

I was considering building a formal "Milestones" page which listed all the current milestones under a parent and their respective progress.

Yeah, I'm pretty sure there's no difference.

What behavior do milestones have that subprojects lack (or vice versa) which is relevant for progress tracking?

Oh maybe I forgetful. Anything can track progress.

Because they track progress.

Why would you want to set those up as milestones instead of subprojects?

@epriestley do you still feel strongly to not do this? I presume it's just gated and easy to ship.

Milestones are a special kind of subproject for organizing tasks into blocks of work. You can use them to implement sprints, iterations, milestones, versions, etc.

@aklapper has pointed me to this task at the Wikimedia Hackathon days ago. At the https://phabricator.wikimedia.org/tag/oojs-ui/ we're dealing with the situation that milestones have been put (I don't know if the exact reason was human or program activity) into wrong order. If you show past, hidden milestone columns visible, you'll see that our releases v0.16.2–0.17.3 are before v0.7.0 which is misleading when going through historic milestones.
Would be happy to see reordering possible as well…

I have found that I can rearrange all the columns in some projects but cannot do the same in another one. Here's a screenshot. Now, I am not sure if it is a bug or just a random error.

For example, here is a project with more than 5 columns:

Please read and follow Contributing Bug Reports if you feel you've found a bug in Phabricator.

The rearrange dialogue box only shows a maximum of 5 columns although the project has more columns. This limits the ability of rearranging any column present beyond column number 5.

For those looking for ways to manually move projects until this is implemented: T10350: Scripts to migrate old "points" fields and move projects beneath other projects

This should now be resolved in HEAD of master and stable. Thanks for the report!

ah mkay

These mocks OK?

yeah, i'm almost done, just a little dinky diff

In the results, show if you're watching a particular project or not?

OH

Maybe I'm misunderstanding what you mean by "attributes"? What's an example of what you mean in some other search engine?

But since you claimed it...

I'm going to add the attributes too

Presuming resolved; you can already use Watchers: viewer() or Watchers: yourusername to find projects you are watching in an ad-hoc way.

For those looking for how to associate tasks to columns - reference the following from T12074:

Yep, thanks!

It's possible T10872 is also related/is a duplicate.

With subprojects, #project changed to mean "that project, and all its descendant projects", but any(...) and not(...) still mean "just the parameter, exactly". I think viewerprojects() and projects(user) are also "just the parameter".

I can confirm that In Any: does not seem to include subprojects. I tried to make some sense of the way the project search functions work but it's pretty complicated.

Here are some additional use cases and a sample implementation that is a Burn-up chart, not a Burndown chart, plus rationale.