In T15947#19599, @avivey wrote:

Maybe express it as allowed by Policy xxx? (Related to T15277)

So essentially this:

Maybe express it as allowed by Policy xxx? (Related to T15277)

Dear arp, please clone and hack a lot on Phorge :) Thanks and feel free to share any question

What's the status of this one? Just curious if we should fork and hack around it ourselves for now or if it's coming soon.

Abandoning in favor of T15890 and D25774 per previous discussion

I just discovered that sometime we can spawn warnings above the comment box.

@valerio.bozzolan also, triggers don't offer an option to change task space or task access.

I wonder if "Workboard Triggers" may do the job here.

I see. So, is that functionality already a part of arc diff? In other words, if arc work T123 would have worked exactly the same way as arc work branch-name (by creating a branch that's called either T123 or branch-name), then arc diff would correctly link it?

Yes - it works seamlessly because if the local branch has a task number in it, the diff is automatically linked to that task when you run arc diff

I'd assume that it also links the task and the diff together and optionally allows to close the task automatically on diff land?

Just adding references

I'm not skilled enough to look into the bigger picture, however maybe the Edit Column dialog could have a third field apart from Name and Point Limit to also have Task Limit (or Card Limit?). Point Limit and Task Limit then must be mutually exclusive (do not allow to set both for a column, or even...board?), somehow.

OK. If you are partially mentioning nonsenses in we.phorge.it itself, you are indeed right.

We might come from different user journeys.
Your users might be aware what the project means, and that the project (and its workboard) is archived, and they do have an initial reason to look at this archived workboard (e.g. default view is not "open tasks" but "all tasks")?
My users clicked an external link to some project tag in something called Phorge, and that project has been archived in the meantime, and that project is set to show the workboard by default, and that is now just empty columns (as the default view of workboards is "open tasks"), and that is confusing and unhelpful.

I mean. See this archived Project (archived Milestone), that is linked from our changelogs:

For example, some people then may ask "why my default view was changed?" and they will start manually "rollbacking" this to their desired view (e.g. showing closed tasks, from the Workboard, with a filter "Show all tasks").

Premising that I like the implementation but I think it's not the desired solution.

Premising that the root problem is that it's difficult to understand if a project is archived just looking at other parts.

Cleaner attempt in D25546 Diff 2113.

Thanks for the pointers, I really appreciate them.

/settings/panel/multifactor/ requires users to add a custom Name so there is likely code to adapt/reuse for /settings/panel/apitokens/

I think the EditEngine is what's used to create the actions form, and it has some sense of the object's status (see for example the available actions on Revisions - these change based on the revision's state).
Maybe it can get an additional "field" for this warning, and display it based on task status.

I remain unhappy with my code in D25546:

• Phorge lacks a method "give me all engines for this application".
• PhabricatorApplication offers nothing related to engines.
• PhabricatorEditEngine::getApplication() does what I want exactly the other way round: it returns the application for a given engine.
• PhabricatorEditEngine::getAllEditEngines() is confusingly named. It only returns EditEngine keys like calendar.export or maniphest.task but not actual engines or engine classes. ($engines = id(new PhabricatorEditEngineQuery())->setViewer($this->getViewer())->execute(); returns the actual engines, as already used by this code.)
• I cannot find some mapping between EditEngine keys (like maniphest.task) and either PhabricatorPHIDTypes (like ManiphestTaskPHIDType) or their TypeConstants (like TASK) either.
• getEngineClassName() exists but only in a SearchEngine/SearchQuery context, not in a EditEngine content (and I cannot find its constructor)