- User Since
- Jan 15 2015, 3:53 PM (226 w, 6 d)
Aug 21 2017
I can say that this feature would be very nice. I have two LDAP servers in my case and other tools/services that I use allow me to configure both (whether as primary/backup or round-robin). It would be nice if Phabricator allowed specifying multiple LDAP server host names. Of course, I tried that before adding this comment got this error:
Feb 2 2017
That sounds good to me.
I have an infrastructure project that mostly involves writing/updating documentation. It is somewhat of a hassle because while closing the task when it is done is not usually a problem, I have found that it is not common for people make their way over to a task after updating the documentation to comment on it (when the task is still not yet ready to be closed).
Sep 24 2015
Apr 24 2015
Thanks for implementing this! I will definitely make use of this feature.
Jan 15 2015
Sure. We could change this, but currently we never auto-inherit projects. For example:
- revisions don't auto-inherit repository projects;
- Phriction pages don't auto-inherit parent projects;
- blocked tasks don't auto-inherit projects of blockers;
- revisions and mocks don't auto-inherit task projects;
- Almanac devices don't auto-inherit service projects.
In all these cases, I think the rule is correct. I'm inclined to think it's the correct rule for Diffusion, too -- although changing the rule would be fine for #phacility on this instance, I don't think a repository project tag necessarily applies to all commits.
Currently, I have my projects/repositories associated in a one-to-one
relationship. However, I would like to be able to possibly have a
many-to-many relationship, which would make the most sense to me on a
Correct. If I specify a project hashtag, then a commit shows in the
project's feed. I'd like all commits for a given repository and branch
to be automatically associated to the project such that if I view the
commit in Diffusion that the project is listed under Projects and so
that if I view the project the commits appear in that project's feed
That is correct. Right now, only commits which Ref or Close a Maniphest task associated with the project or which include the project's hashtag appear in the project feed.
Let me take another crack at a concise problem statement: