Thanks @mcorteel, I'll take a look.

@mcorteel I have the same problem, arc unit only works with phpunit 5.7. If I use 6.5, it fails. Do you have that patch anywhere with public access so we can use it while it's not published?

I'm having problems with script-and-regex too. I have asked in the community forum but without luck. I’m trying to add phpstan to the arc lint workflow, as explained in the documentation, but I’m unable to capture the error message. Here are my files:

In T7091#111368, @epriestley wrote:

ScriptAndRegexLinter needs to be modernized, but is strictly more powerful than the proposed linter. Something like this will implement your desired lint rule after the linter modernizes:

"todo": {
  "type": "script-and-regex",
  "script-and-regex.script": "grep -n TODO --",
  "script-and-regex.regex": "/^(?P<file>[^:]+):(?P<line>\\d+):/"
},

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 } ?

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.

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.

It has been asked in Q287 too.

There is a similar discussion in T7676.

The same problem here. I have a lot of 'pending' audits because I did the commit and audited it. They have an accepted label in audit list, but 'partially audited' if I open the audit. It happens also if I'm the only member in the project that is needed to audit.

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.

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

Hello all!