I am a a physicist and software engineer specialized in server to server communication, mainly using Java, Python, c++ and c
I was one of the last developers involved in Scarab, a Java based Issue tracking system. Two years ago we decided to abandon Scarab and replace it with Phabricator. Unfortunately we committed our move to Phabricator just 2 weeks before Phabricator decided to shutdown.
I hope that Phorge will keep alive for some years.
No, the filter only fires when the value is set to true. When the value is not set or set to false, the filter does not fire. I believe that for boolean fields there is no way to distinguish ‚false‘ from ‚not defined‘ which might be the root cause of the issue.
Furthermore when i define the field as required, then the only accepted value for the field is ‚true‘ which makes no sense at all to me.
Definition of the custom field that is queried:
Its basically a predefined query that is called via conduit:
The added [xxx] lets people easily see right in the email inbox if something needs immediate response without need to open and read the email or login to phorge to check for example the severity or priority of a task. We found that adding such a marker was the easiest way to go. However, if there are better solutions, i am eager to learn about them. Would tags and columns (what are columns in this context?) help there?
@valerio.bozzolan Thanks for the feedback and sorry for the late response. I must admit that i forgot how we eventually fixed our issue, i only recall it was more about "avoid the issue" and less about "fix the issue". I also completely forgot about this Maniphest. Hence, it is OK for me that it is closed by now. sorry for not taking care about this earlier.
@avivey Thanks a lot for the hints. I will take a look at the Spaces. That sounds like it could be helpful for our purposes.
@rraval Could you or someone else verify that a project that is made visible only to Administrators still shows up when a user opens the search selection list on the Subscribers field? And is this considered to be a bug or a feature? Of course i can set up a new Task for this if that makes sense.
@rraval Right, i overlooked this setting. I managed to hide most projects from the Subscribers Search panel. We also have reduced the number of Projects to keep things more tidy.
We use Projects for grouping users into teams. But unfortunately every user can see all Projects and assign them as subscribers to Tasks, regardless if they are members or not. Normally (in our case) Tasks are only relevant for users in the same project. Having the other projects displayed in the subscribers selection is unfortunate in this case.
I inspected the code in some detail and i figured out how to get the default value of a custom field. In a first attempt to solve my issue i tried to only show a field value in the property list of a Task if its value differs from the field default value but this does not work because i can not get the current field value this way:
We are now at a decision point where we either install Phorge from Scratch or migrate Phabricator to Phorge.