- User Since
- Apr 2 2014, 11:33 AM (280 w, 4 d)
Mar 9 2016
Mar 8 2016
Mar 1 2016
Jan 26 2016
Sorry, I had locked the project field in the edit form for that user and it wasn't pulled through.
Jan 17 2016
Also having this issue on our install on all projects with characters like (, ), and *
Dec 30 2015
Excellent, thanks for explaining!
Also, adding / removing members from superproject / subproject isn't working.
When you make a task in a subproject, clicking on the project name in the task detail view will give you a 404 as it tries to access /tag// (as there is no project tag set on sub projects)
I know this is all prototype at this stage, but where's the best place to highlight bugs with the current implementation? Should I just file a bug report in maniphest?
Dec 27 2015
Dec 22 2015
Oct 15 2015
Sep 29 2015
Aug 23 2015
Firstly, I agree that stopping real time support is a good idea, It's never a great situation to be distracted whilst in the middle of things. - Many of the first time install / issues could be solved with fool proof installation process or something like an official Docker or Vagrant image.
Aug 17 2015
Aug 12 2015
Aug 10 2015
Have implemented using local patch, working well.
Messed up Status + Priority, I meant Priorities - Must be monday morning!
So I'm guessing something like the following is a bad idea then.
Aug 7 2015
Is it worth filing these bugs in the future, or should I hold back?
Jun 30 2015
Jun 10 2015
Jun 1 2015
Feb 3 2015
Jan 12 2015
In our installation, we have it so that if you make a task attached to a project, it sets the default visibility to that project.
Jan 11 2015
Jan 9 2015
Diff here: D11297
Managed to get this working on our install, will bring together a Diff after testing.
Jan 8 2015
Jan 6 2015
Jan 5 2015
+1 for mobile browsers
Dec 22 2014
Oct 28 2014
It would be good if this could happen the other way around, making task status influence which column the task is in