- User Since
- Jan 7 2014, 5:35 AM (517 w, 7 h)
Mar 19 2014
Feb 25 2014
Even I don't care about that and I am the biggest jailing fan ever :)
I think keys should still be global as its better UX to refer to a task as Tx, not CLIENTSAREWONDERINGWHYTHEYNEEDTOWRITETHEIRCOMPANYNAMEINFRONTOFEVERYTHIING-Txxxx
Feb 17 2014
Another use case:
I have found myself wanting to apply one or all of the filters below to a Maniphest task search query:
NOT assigned to
NOT authored by
NOT subscribed by (to find if I should CC someone, applies to small projects, usually a part of a bigger query)
Title does NOT contain
Title contains (right now its searching in title and text, which gives too much false positives)
the "order by: date created" filter would satisfy the initial use case, however I kinda hijacked this task and Pivoted it to be more general
I want to see if some other member has created a project to check if I should join it (being the all-knowing Admin), or whether its just spam/testing.
nice ticket number :D
Feb 12 2014
ctrl or shift select 2..N tasks and then drag&drop them similarly like now with the 1 task. It should preserve the order they were in.
An alternative might be to show CCs with policy failures in a disabled style.
Feb 11 2014
thx, thats a good work-around actually
yeah, I've often canceled my changes in the Edit page only to make the same changes using the Comment Action thingie in the View page. Simply because I want to comment my changes and I want the comment to be in the same row block as the changes, not a separate row block.
just disabling Enter would be enough, Its hardcoded inside my brain that when I search for something I hit Enter to see it. I've lost large lists of carefully selected dependencies because of this nasty habit multiple times :(
Feb 10 2014
Already implemented according to doc:
Feb 9 2014
Feb 8 2014
This feature would be extremely usable (as in good UX) when you have multiple projects that are not associated.
For me I cannot solve this socially as the people in question change all the time as I take on new clients. Its more time-costly (for me) to teach the world, rather than make the workflow a bit byreocratic.
Feb 7 2014
I use the same trick when I (think I) need to buy something big. It goes into a list. I prioritize it only after some time has passed and if after a few weeks or months I still feel like its important, then I buy it as opposed to buying the damn thing the first moment I think I need it. Its the same with tasks.
I would still like All users to be able to edit/view the priorities of tasks, but I just want to move assigning priorities to a time after the task is created for the reasons I mentioned above. Its like a cool-down period.
Feb 6 2014
what about the "me too" comments then?
Adding Google Calendar support would make the Calendar immediately useful to a lot of people. Right now the Calendar is just isolated and thus largely unusuable. Eventually it would be great to add task deadlines and milestones to the Calendars (if/when these features are added).
Forcing a Triage also enables people to add dependencies and subtasks, otherwise they might forget that, because one can't add any dependencies while creating a task.
I think it would be OK if the custom company logo would also point to the Phabricator root as this is the expected behaviour from a topleft icon/logo.
I would like to voice my support for adding the logo before Phabricators logo: MyCompany > Phabricator
Feb 3 2014
Jan 31 2014
The default View policy of "No One" also affects this bug
Jan 30 2014
@epriestly we discussed some use cases for software companies with client projects. I'm linking the IRC log here with the hope that maybe there's a few new pieces of information or even an useful new use case: https://secure.phabricator.com/chatlog/channel/6/?at=113588
Subtasks would be a great way to explode larger tasks into smaller and smaller tasks (recursively). This in turn would improve the accuracy of estimating schedules based on custom time cost fields.