@epriestley Maybe one to consider: you must have a default workboard column for a project; the default workboard column cannot be hidden; milestone workboard columns strictly sort after project workboard columns. The combination of these three means that I have a project which is strictly split into four milestones, but its overall workboard view always includes an empty column before each milestone column. Is it worth filing a task for this?

Also, the workaround now is to do a search so it's not horribly broken, it's just not as great/fast/efficient for us as it used to be.

@chad yeah it's been a very long time, a year sounds plausible. I keep meaning to share this with you guys but I had been putting it off for a very long time as it hasn't been as important as other items in my world. One of the challenges with these sorts of things is that even though people in the field may be hitting the issue, they're usually trying to do something and in their workflow and don't bother sharing it... it was only when I asked around that people were like, "yeah, I miss how it used to be a long time ago..." etc.

Yeah, looks like Tasks were removed from ProjectProfileController in January of 2015. rP3bc54c204

I honestly can't even find where tasks was the default on project home... How old was your instance? I checked back 1 year and it was a side-nav icon then, so it's been over a year since we moved tasks off the project home page.

It isn't a common use case, actually. If it were we'd be very aware of it given the significant length of time it's already been at HEAD.

@chad I see - my gut is that this is a common use case and that most teams will not take the time/energy to do this customization (or realize it's possible) but that they'd value having an easy way to see tasks as the primary use case of clicking a project name. Just my 2 cents.

We'd prefer a customizable solution vs a hard wired one, if that's what you mean, as that benefits the most scenarios.

@chad thanks - so sounds like you don't think this would be beneficial to everyone to have?

T10308#158036 has a custom panel you can add to your install to shortcut and make adding this locally to projects easier.

Long term you can expect Projects will pick up features from Dashboards. We'll let you customize the nav, customize the page, and customize the landing page. You will be able to recreate the old experience if you so choose.

I appreciate that we can customize this, however this solution is not feasible for us as we have dozens of projects and add new ones regularly.

One additional usecase for subprojects: it would be very nice to be able to move subprojects between different parents. In particular lets say we have
team1 > productA
team1> productB
team2> productC
and as a result of a re-org or some other influence productA moved to team2. To do the move now we'd have to create a new project, reconfigure it (cloning the workboard), and mass change the labels (remembering where in the workboard every task is).

In T10350#167753, @rbalik wrote:

This is useful, but are there any plans to add this functionality to the GUI? Would be nice to have for when we're doing some housekeeping

This is useful, but are there any plans to add this functionality to the GUI? Would be nice to have for when we're doing some housekeeping

See T10350.

Is there any way to take an existing project and make it into a subproject? I don't see any discussion of that in here

See T10326.

We had a user that was confused and frustrated because on the task view page projects are under a "Projects" field but on the edit page are under a "Tags" field.

If anyone else has the same problem, here is the solution. You have to edit maniphest.fields and not maniphest.custom-field-definitions.

Isn't that about editing the config to have maniphest.fields say "isdc:sprint:storypoints": { "key": "isdc:sprint:storypoints", "disabled": true } ?

It would be handy if subprojects and milestones would inherit some of their parent's settings (like icon, color, policies, and picture) by default.

In T10350#166563, @rfreebern wrote:

@cmmata Configuring Custom Fields may help. In your installation, you'd navigate to /config/edit/maniphest.custom-field-definitions/ to edit the Maniphest custom field configuration.

@cmmata Configuring Custom Fields may help. In your installation, you'd navigate to /config/edit/maniphest.custom-field-definitions/ to edit the Maniphest custom field configuration.

How (or where) can I remove "old" points custom field? I successfully migrated all points to the new Maniphest field, but now I have two story points fields. I'm taking a look at the database, but there's no direct field in maniphest_task. I suppose it's the reference in maniphest_customfieldstorage with fieldIndex yERhvoZPNPtM (at least in my case), but I prefer not to alter a database without knowing all the places I have to make changes.

Yeah -- it's not very clear on its own, but this comment is specifically referring to that issue:

Hmm... maybe I'm not explaining my expectation well, but the "issue" I'm referring to is the fact that after steps (1)-(3) I now have a task that is in the "Subproject A" column in my "Project X" workboard but is not *actually* in Subproject A anymore.

T10486 is related; T6027 and T5214 are somewhat related.

Thanks for looking @chad

Does the task go away from the workboard when you refresh? I think that's the missing step here, that you're editing the task on the workboard.

I followed steps listed here but didn't get your same outcome. Can you clarify the steps to reproduce, the expected result, and the version of Phabricator you're using.

Can you fix the issue with arcanist in near time, that arcanist does not accept milestones at differential diffs? This is very annoying.

D15454 changes the wording to:

We should probably change the text on "placed up for grabs" to "unassigned from X". I don't think we use that term anywhere else nowadays, either.

This is particularly problematic in the UI when you need to revert the first change to a task since creation - there doesn't appear to be any way to find the initial assignee of https://phabricator.wikimedia.org/T129128#2105237 for example

It's mainly the projects that I want to see as well. Although there has been talk of priorities etc. as well

In T10493#162973, @epriestley wrote:

It looks like the root problem in all of the downstream reports is that projects, specifically, are no longer readily available (although they previously weren't on emails deeper in the thread, either).

"implement Gmail in Phabricator"

Yeah, this was mostly-intentional while resolving T9527 / T7661.

Ref T10004.

I have a vague feeling it's related to cleaning up the initial create transactions, that is, we used to show every field on the first transaction, which was silly since you could see what all the initial values are above.

Worked like a charm! Thanks.

When creating the first subproject there is a note that all members of the project will be moved to the subproject.

In T10349#161180, @cburroughs wrote:

Initially, I've found myself digging iterations for the magic workboard columns even for "evergreen" things that are not really iterations. I wanted to reorder them, but I'm confused what the UI is trying to tell me. Can I not re-order iterations, only control how they appear relative to "normal" columns, or is this busted?

If I was to delete the broken project (bin/remove destroy PHID-PROJ-...), would that clean up the database in such a way that the broken links were also removed? Or would that break the database even more?

In T10350#160815, @urzds wrote:

[...]
It appears impossible to clean up the relation between the task and B(Z) / B(A) from the UI.

Initially, I've found myself digging iterations for the magic workboard columns even for "evergreen" things that are not really iterations. I wanted to reorder them, but I'm confused what the UI is trying to tell me. Can I not re-order iterations, only control how they appear relative to "normal" columns, or is this busted?

Internally, we track "explicit members" and "implicit members".

Parent projects can not have explicit members. The explicit members are moved.

However, all members of subprojects are implicitly members of ancestors, so they're still present as implicit members of the parent.

I'm hoping to navigate this without adding more concepts to the UI like "explicit members" and "implicit members". One thing I'd like to do is show which subproject(s) a user is a member of in the "Members" panel for parent projects, which might help. We could also add a line of explanatory text, and/or rename the panel to "Members of Subprojects", although both clutter the UI to explain a one-time facet of the model.

When creating the first subproject there is a note that all members of the project will be moved to the subproject. In fact, members were copied to the subproject

We just played around with projects, subprojects, and milestones as we wanted to figure out a nice way of organizing work. We fell over a few inconsistencies/issues/bugs:

@20after4 It would be helpful to get a sense of what your ideal tree looks like -- would adding the immediate parent project always be sufficient to disambiguate things? Or would it produce 30 different projects named iPhone > Bugs because the full hierarchy is CrazyFlaps > iPhone > Bugs, FlappyFish > iPhone > Bugs, etc? Or do you have a mixture of hierarchy depths?

Maybe a config option to make your own regex for display? Or just a select of a handful of options like

If the parent is already a parent project of some other project, it has no direct members, so nothing will be copied. --keep-members parent should do what you want, provided you move "Members" first, before "Subproject A" or "Subproject B".

This is covered in the conversations above, but the short answer is: There are 16 possible levels of subprojects, so there isn't any clear path forward to us guessing what you want displayed, and thus it is up to you to name Projects accordingly.

When searching for a subproject you don't see the parent project in the typeahead results:

With --keep-members parent, the child's members will be wiped out. If the child is becoming a milestone, nothing else happens. If the child is becoming a subproject, the parent's members are then copied to the child.

@nochum, can you explain what you're trying to do in more detail?

Would be nice to be able to skip --keep-members altogether and not move the members over at all. Thanks for the script!

I was using the move_underneath.php script and noticed that now some tasks are assigned to several milestones in weird ways.

I had to add an explicit cast to int when I ran the conversion script, but other than the 3 or 4 tasks which lost their points value, everything else worked nicely.

Some browsers (Safari, at least) also take several seconds (well, two seconds?) to render title attributes after a hover, which reduces their value as a way to quickly get more information -- I can click the "Edit" icon and find the information more quickly than Safari pops up the title text.

You're right. I think it's the best alternative while there's no pop-up. We'll go with this option, because using milestones that way can become a problem in the future.

In T10349#160305, @cburroughs wrote:

A task tagged with a sub-project, is still in the parent project, right? So it hasn't been "removed" from Dashboards

There's no space to show that columns in cards, but would it be possible to show them in a tooltip?

After observing the feature on this install I feel like the email messages are misleading, or I'm confused about how sub-projects work.

@epriestley It would be funny to read that book :)

Oh, yeah I assumed they would be hidden.

We should maybe hide the tags for archived projects on worboard cards, I notice WMF has a lot of this:

I will report you to the workboard police on T10215 if you keep it up! You better check yourself before you wreck the project roadmap for weeks by derailing it into abuse cleanup tools.

Every instance? Because I did it lots.

I have replaced your dumb 1x1 transparent GIF with a fearsome tyrannosaur.

1px gifs are awesome at being cover photos.

I really like the look of the inverse tag, although I haven't personally felt too much confusion about milestones vs nonmilestones on project pages.

In T10349#159831, @cmmata wrote:

So is there any official/recommended way to work with global milestones?

D15289 should give you better tools for gaining an advantage over your adversaries in hostile departments.

I can update the script with a "no int check + warn on weird values" version if anyone wants that but isn't too comfortable with PHP.

Yeah, the int is mostly out of an abundance of caution. There's currently no float custom field type, and if you previously used string you probably need to massage values anyway since some of the fields may have strings in them (I think WMF had a few strings like huge, epic, etc). You can comment out the int check safely, but may need to add some code to examine $value for usual values if you do (or accept that they'll probably be cast to 0).

we could invert tag colors on milestones to stand out more.

I'd like to be able to search for watchers like I can for members:

• If you or an overwhelmed co-worker over-zealously watched/subscribed to too many projects, it would be nice to be able to undo that without playing whack-a-mole as emails come in a week later.
• If people are spying on my projects, I need some sort of counter-espionage capability.

That 'int' requirement is definitely misleading, since the field supports fractional point values (which makes me happy, since we have .5-point tasks in our workflow).

Hello all!