[19:01:21] <Valerioboz[m]>	 <olle> "How do I convince CTO to..." <- With Phabricator you can, in one place, have a calendar, tasks management, kanban board, git repositories, svn repositories, mercurial repositories, and it quickly allows the creation of separated spaces where only few people can create something, see something, or edit something. It also has nice APIs to do everything
[19:06:42] <Valerioboz[m]>	 With Phabricator you can create different task creation forms to speedup creation of multiple reportings for different frequent situations; you can have a task assigned to multiple different projects, in order to allow different teams to work on that single Task, organizing that Task with high customization for each competence (for example one team has that task under "Blocking" kanban column, one team has that task under "To be
[19:06:42] <Valerioboz[m]>	 released" column, one team can have that task under a "Review security" column, something like that)
[19:16:40] <olle>	 Valerioboz[m]: Well we're sadly already using Jira for company-internal tasks. This is more about getting rid of the community bug tool.
[19:17:06] <olle>	 Maybe you can add your comment here? https://we.phorge.it/Q33
[19:17:13] <olle>	 "Pros and cons compared to Mantis"
[19:27:01] <Valerioboz[m]>	 <olle> "Valerio (boz): Well we're..." <- In Jira is nearly impossible to customize per-task security settings, so you cannot change who should be able to see that specific info. Also, Jira is usually not integrated with your  kanboard platform or you repository
[19:45:16] <Valerioboz[m]>	 Jira is more ticket-oriented while Phabricator is more team-oriented
[19:48:57] <Valerioboz[m]>	 (With "Jira is ticket-oriented" I mean is more to receive boring requests coming directly from customers and to be closed asap. While Phabricator is more oriented as internal team management and documentation platform, so also to document how you are doing something, also to quickly find how your team fixed something already, etc.