Some sketches in M1466, but essentially we'll give you some default options, and a "navigation builder" which you can select on a per-page basis. Based on the mocks, the "hierarchy" moves to being a side navigation, and defaults now to one level. From that you can "Manage Page" and change the default for that page. Rough thinking is:

Combining Draft / Archive into a single task since it's easier to build both at once.

We're going to likely move the hierarchy and give you control over what it shows. Merging in favor or T8552

Regression possibly caused by this: https://phabricator.wikimedia.org/T137394

Create a custom query inside Phriction, save it, then go to Dashboards and make a Panel with that query.

Thank you we basically created two projects to group the members into those two projects and i removed myself and only stayed in one and that seemed to kind of work. I see only the files i expected but also some deleted files history that is greyed out. It would be nice to have an easy place to put custom queries to be used for each of the apps but I love Phabricator so keep up the good work thanks.

Your best workaround for now is multiple text panels for each organization.

T11161 is the follow up for Dashboards

I'll create a separate task to re-think Panel creation UI.

You're not creating a custom query, at least in that screenshot. The query is "All Documents", which is what you're getting.

I was able to reproduce this on a Phacility test instance as well: https://test-ftzenxozitfe.phacility.com/phriction/edit/?slug=/

Anchor tags got cleaned up in D16083.

I think this pretty much boiled down to three technical pieces, all now better covered elsewhere by more specific tasks:

Copying in some context from elsewhere:

I think nowadays the biggest issue (as it is the most work to manually correct afterwards) is two folks editing a task description at the same time and silently overwriting.

+1 for iframe syntax - don't need google docs but we've been wishing that we could embed iframes into our phab diff summaries.

Not sure if this should be another bug report but the / that is added at the end causes issue when using anchor tags i.e if [[ ../2016.19#gotolocation ]] was the markup the link would also be broken by adding a / at the end.

It's not email client dependent - Phabricator is writing out the wrong URL when sending email.

Which email client is this about?

Beat me to it :P

We'll fix this eventually, but probably not until the next time we do major work on Phriction (T9379) since the impact is very minor.

Looks like using [[ Prioritization ]] doesn't trigger that it's a good link. But [[ prioritization | Prioritization ]] does.

Well we could use Maniphest for commenting on documents, except that Maniphest tasks don't have a hierarchy to them.. neither do all of those other applications.

T3353 isn't specifically all about "review" if you read through the task. That task is the currently point for all things "we want to discuss changes on a document". I think that could include:

We're not signing off on the textual or structural changes, we're just agreeing that the ideas expressed in the document are what we all understand them to be.

Discuss potential changes.
Make the changes.
Then record a comment from each person signing off on them.

That task seems to be about reviewing structure of the document whereas we want to discuss ideas and content (and we don't need or want a formal review process).

T3353 is the "Review changes in Phriction" task.

I think a way of addressing the issue is to set the "There are 10 previous comments (show all)." bar that appears in transactions to at least comments that were made after the last change to the document.

• If /w/x/ exists and is titled "History of X", it would be nice if [[ x ]] generated a link with the text "History of X" instead of a link with the text "x". Today, you must do [[ x | History of X ]] to get the proper link text.

Cool. Yeah, that all sounds good to me.

Yeah that was my plan; relative links on non-Phriction pages just won't get marked up.

(If the current page isn't a Phriction page, I guess just don't mark the thing up?)

That seems reasonable to me. I like using ./ to opt in to this and not making it the default.