I do have similar problems with the keyboard shortcuts for displaying the Conpherence column (with "\") and the Darkconsole (using "`").

Yes, I think that's what I've observed as well.

This has tripped me up a few times (maybe since arc was made great again?) and I think it happens when you do arc land foo instead of arc land in foo.

This solved my problem, thank you so much.

Does this fix it?

Use bin/search index --type task to rebuild the index.

(or any id)

Instead, it now throws this exception.

I encountered this on a svn repository, but what do you do for git repositoires where "label: one line summary" is considered best practice for commit messages?

In general you'll have to steer clear of any "label: field" in your titles.

"Tests:" and "Test Plans:" are both valid labels. See https://secure.phabricator.com/diffusion/P/browse/master/src/applications/differential/customfield/DifferentialTestPlanField.php;aa6c993848797d792a886b4a570f20ca897ade7e$164-170

In T10311#158135, @chad wrote:

Thanks for clarifying!

Thanks for clarifying!

I just clarified the description. Maybe I made it still too difficult. Let me shorten it up.

I've read this a number of times and I don't understand the reproduction steps. I can't offhand reproduce anything, but I'm probably missing a step?

What is "it" in your bug report?

That actually was going to be a suggestion once discussion started :-)

Milestone Columns aren't hidable currently, we'll remove the option and make it disappear if the Milestone is archived.

This effects me too, I'm on a freshly installed Ubuntu 15.10 server. On master:

You are welcome to reproduce on a Phacility test instance if you are unable to update, but as a rule we only take bug reports at HEAD.

Rule #1 of bug reporting:

Did I miss the Dungeon Master rulebook for quest value assignment?

I mean, far be it from me to declare myself Lord King Questmaster of the Realm, that just seems like a lot and/or not a lot of valuable and desirable Quest Points for this particular task.

Is this REALLY worth 12 quest points!?

I think @Pawka is west-cost install administrator, they have (at least) two totally separate installs.

Whelp, just need @yelirekim to install it then.

I guess that isn't very helpful for practice. :)

I think I could just build this as an extension? (I've never built one, so I'm a little interested in building one for practice)

Prebuilt, hard-coded panels feel weird to me and I'm hesitant to introduce them just to make the transition easier.

I use this link a lot:

Would you be open to a "search for open tickets in this project" PhabricatorProfilePanel?

and @jillian thanks for following up from Twitter. We get lots of rants sometimes there, but it seems rare that people then come here and give us the details. We're actively working on Projects, so this feedback is very useful.

I have a few thoughts, not sure what @epriestley might have in mind.

In T10308#158023, @cburroughs wrote:

We removed the default task link because in many cases, the link to all tasks wasn't used, wasn't useful, or wasn't the best link (e.g., maybe several links or a link with different filters would be better). Particularly, the link was often redundant when projects use workboards.

I find myself clicking on a project to get to a list of tickets and then realizing that doesn't work often enough to notice. Maybe I am just used to the old way? For projects I use a lot adding dividers, urls, and motivational quotes has been nice. But customizing every single little "tag" project with a unique url doesn't feel super fun. Would you be open to a "search for open tickets in this project" PhabricatorProfilePanel?

We removed the default task link because in many cases, the link to all tasks wasn't used, wasn't useful, or wasn't the best link (e.g., maybe several links or a link with different filters would be better). Particularly, the link was often redundant when projects use workboards.

In T10308#158019, @chad wrote:

On images, the workboard design in https://secure.phabricator.com/M1450/2820/ has a new "columns" dropdown, which is not yet implemented. This will allow you to "Group" the columns on other variables, like assignee.

On images, the workboard design in https://secure.phabricator.com/M1450/2820/ has a new "columns" dropdown, which is not yet implemented. This will allow you to "Group" the columns on other variables, like assignee.

thanks for the info regarding being able to customize the project menu!

For (1), you can now edit the project menu and add relevant links. We removed the default task link because in many cases, the link to all tasks wasn't used, wasn't useful, or wasn't the best link (e.g., maybe several links or a link with different filters would be better). Particularly, the link was often redundant when projects use workboards.

FWIW, I'm running 2015 week 43.

We mitigated with:

In general this falls under "feedback" or "design feedback" (see T10208). We don't have any decent mechanic for taking and holding these opinions in Phabricator. For "design feedback" we currently limit it to what is on the current Roadmap. This helps our small team (2 people) remain focused on building and thinking about the current product.

I'm going to merge this over this since it's not a bug report nor a valid feature request (since a per user option already exists).

Thanks !

How can I reproduce what you've done to get the same error?

I followed your guide. I ran the ubuntu installation script, followed the instructions for setting up the db, but even before then, the web app was redirect-looping with just those three RewriteRules in place. The REDIRECT_STATUS hack was the only thing that seemed to fix the initial looping but it's not catching the /auth/register loop.

Actually on a real phone it's fine. I guess just something else is causing it at small breakpoints.

I'm not able to reproduce any issues installing Phabricator. Can you provide reproduction steps, specifically?

(Also I assigned this some quest points, but I guess those don't generate transactions yet).

On a fresh installation

I don't have any ideas on how to troubleshoot this, since it's most likely to be between the webserver and your browser and I've never run into it personally.

Using PHIDs instead of slugs is likely a workaround, but possibly not helpful depending on what you're doing. D15214 should fix the root issue. Thanks for the report!

Never mind, here's an example:

Can you give me an example of a URL which hits this?