This report doesn't appear to describe a specific problem.

I did indeed update across those 3 revisions you listed; I was previously at October 11.

It's intentional that we normalize the slugs to try to make typing URLs a little more forgiving: For example, if you go to any of these links:

I think I see the issue.

Just to set expectations:

There were some changes to slugs about 6 weeks ago (D14260, D14261, D14287) but I don't think they would have affected this.

We just did a visual refresh, but this didn't touch anything mechanical about Phriction. Not sure how it might have gotten in that state.

Since we can't reproduce this, I'm not sure how we could fix it.

This task doesn't contain enough information for us to reproduce the problem you're encountering. Please see Contributing Bug Reports for an outline of what we need in an actionable bug report.

name

I have made these changes to the planning document which are hopefully more clear:

Just to confirm, there are no plans to implement this within some timeframe, right?

I too cannot recreate it.

ok Thank you

Steps to reproduce would be helpful. I tried to reproduce the error naturally and am unable to. I tried:

Your options always are, pay for us to build is soon, or wait for us to naturally prioritize it. We try to "plan" as little as possible so we can be more flexible.

Sorry for the misinterpretation. Just to confirm, there are no plans to implement this within some timeframe, right?

@UsmanKhan, you're looking for https://phabricator.wikimedia.org

That isn't what the planning document is intended to convey. I'll update it to make it more clear.

In T3725#145540, @epriestley wrote:

@polybuildr, please see Planning.

I've been using the ((alias)) syntax pretty frequently and it's been really helpful -- we have a bunch of documentation we point people at all the time, and before Phurl I'd open a new tab, search for the document, copy-paste the URL, and maybe put some [[ ... | nice title ]] syntax around it. Now I just ((thing)) and it's way easier. The search + copy/paste workflow wasn't hugely time consuming, but it was really annoying.

Interesting. Thanks.

Phurl (T6049) is still a prototype and not yet documented.

@epriestley in above comment you've used double parenthesis syntax ((text)). I can't find reference to it on the Remarkup documentation page.

@polybuildr, please see Planning.

As requested by Chad, an attempt to describe our use-case:

Are there plans to implement this anytime soon?

This Phabricator install is not related to Wikipedia.

We don't plan to support these webhooks.

I read the diffusion_updates doc. I just say it would be better if Phabricator support the webhook feature provided by Bitbucket/Github. A lot projects are hosting on these provider, and it will be an easier life to just use standard git tools.

I'd also recommend reading the documentation on Diffusion Updates: https://secure.phabricator.com/book/phabricator/article/diffusion_updates/

See Contributing Feature Requests, specifically we need to know the core problem we're solving, not the feature you want built.

Some related documentation, bitbucket webhook docs

Cool. We definitely want to make dashboards easier to use in the future, but it's entangled with a bunch of "Welcome" / "Role Profiles" / "New User Experience" stuff that makes it a big project. Maaaaaaaaaybe Q1 2016-ish-ish. Maybe?

That gets me close enough! There wasn't anything in the Maniphest documentation I found about being able to create a panel and then link it. This is pretty much what I needed, though.

Just to make sure I remember things, specific issue is:

Alternatively, you could use a dashboard to provide the "executive dashboard" view, and bring text into that with text panels:

1. Create a query in Maniphest with the stuff you want to show.
2. Save it as a named query.
3. Create a new Dashboard panel with that query.
4. Embed the view with {W...}. For example, here's {W402} on this install below (which shows a few recent tasks in Phriction):
5. You can delete the named query now.

We need to hard-wire stuff like that, Herald can't do "after X days" and I don't plan to add that capability in the near future.

See Planning and Roadmap for details on how we build Phabricator.

That sounds great... is there an ETA for the new ApplicationEditor?

The garbage collection simulator is good exercise for that I hear.

Haven't seen any more issues since rolling the server; I'll keep my eyes peeled.

Looks like maybe I got all the cases? Tables seem to work fine too.