I think it's very unlikely that we'll ever write some kind of script to just fix this stuff. I suspect such a script is impossible to write (i.e., the "correct" value for most fields is ambiguous) and that maintaining it is very difficult.

Works now; thanks!

I don't particularly love ASIDE as the trigger, maybe MEMO is a little better? But it doesn't really capture the intent particularly well, I think.

I think this option would very rarely see use, and @avivey's suggestion (arc browse D1234 + use web UI) is a pretty good workaround.

T7789 has some discussion, but there's now a clear pathway forward here which doesn't require anything too drastic. Specifically:

Assuming that the milestoneNumber field will only be used for internal logic to order milestones.

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.

Great, thanks!

There is a discussion about this in T10412: Change Milestone sort options

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.

Thanks! I shall use these powers responsibly 😄

I added you to Community so you should have task edit powers now.

Oops... sorry, can't believe I missed that! I was looking in "Commit Hook: Branches/Tags/Bookmarks" instead of "Commit Content".

Whoops, thanks. This got rebased across 200 years of changes and I didn't re-test creating a credential. D15512 should fix it.

"Is merge commit" detects this.

arc branch and arc list to see open revisions; arc browse D1234 to open it in browser; T5873 for everything else.

That's before you're uploading the diff. If you already uploaded the diff, and say: "Oh, I forget to insert a parameter" for example, you can't use that.

arc diff --plan-changes ?

Awesome! Thanks for the quick reply @epriestley :)

See T5726, T10363.

The data available from feed.http-hooks or feed.query is somewhat limited:

@epriestley I understand you have the setup check - my point is that for RDS users we skip this check when we see we can't do anything about it. And then months later it's forgotten about and we still draw that conclusion.

just convinced that Phab search didn't work and feeling powerless over it

Amazon RDS is incredibly popular so although you haven't seen this request from other installs, my guess is that many are like we have been for the past 1.5 years - just convinced that Phab search didn't work and feeling powerless over it...I understand the squeaky wheel tends to get the oil, but it's worth maybe considering what % of installs use RDS since all of them will have this problem.

@epriestley as the former PM on Gmail I can tell you that for power users this was an incredibly valuable feature - and I've read from your docs that your typical user that your optimizing for is a power user that users Phab regularly. There's plenty of ways to make it discoverable. But I am not the PM here so all I can do is ask...

See also T4103.

@epriestley the UX problem here for us is that all of our employees are using global search when they don't realize it because it's top right when they go to the phab homepage, when in reality they only use Phab for Maniphest tasks. So asking every employee to manually configure these things doesn't solve this problem.

I think this is reasonably supported now.

CircleCI fixed build_parameters in their API so support is now in HEAD of master. There's probably some remaining work but it seems to work properly locally. Let us know if you run into issues with it.

yeah, fair enough. if I build a stronger case I'll reopen/refile

Sounds like this is resolved one way or the other. In the general case, "Another Herald rule" effectively allows you to group, negate, and combine conditions in addition to reusing/including them.

ah, chaining Herald rules, while clunky as a UI solution, probably fixes the more complex scenarios

You can use two rules:

... nvm. brain fart moment.

This should be fixed in HEAD of master. Let us know if you're still seeing issues after updating. Thanks for the report!

as the author of D14104, the advisory update proposal here would make me happy. Its basically taking the class of comments that are suggesting specific fixes or additions and making it more lightweight. One minor ui problem to solve would be supporting pure inserts or deletes.

I think this should be fixed in HEAD, let us know if you're still seeing it after updating. Thanks for the report!

@chad False alarm, I've checked wrong link. Problem existed on Maniphest global rules but it seems it is fixed already on upstream.

I'm still able to select stuff fine and use the form, did you try the dropdown? (I do see the error in the console).

I would vote for X-Forwarded-Proto support in AphrontRequest::isHTTPS

oh, I'm just braindead: I skipped over the nav portion entirely since it wasn't the obvious thing I wanted.

This is already documented, do you have any suggestions for improving the existing documentation?

I wanted to use it for de-emphasis (like you're aside) and for inside of tables for various things. I was also trying to use it for a small "edit this panel" link like the other task but the href on the button is cooler.

oh, cool. That should be documented, but is exactly what I wanted.

I believe it's all straight from MySQL. http://dev.mysql.com/doc/internals/en/full-text-search.html

Yeah, I think changing text size inline often tends to look pretty bad since line heights get all messed up, too.

I'd prefer to not support this. Would like to know real use cases instead, maybe just have lighter text or other means. But generally prefer to keep accessibility issues to a minimum.

Note that you can do this today:

We're planning to do this at some point:

Do you have some examples of things you'd like to use this for?

this task might more generally: support inline remarkup in link names. I havn't tried to make image, bold, or other interesting links.

Elasticsearch may also be a solution. Also, looks like we might be able to detect RDS installs by querying variables in MySQL.

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

Closing this in favor of followups.