Phabricator/For designers

Shortcomings of Phabricator for designers
created after discussion on: https://phabricator.wikimedia.org/T117482

No copy paste for images in Input fields
While it is possible to drag and drop image files, it is not possible to paste them from the clipboard. This is the equivalent of not being able to paste text, but to need to save it as a text file first.

Kind of: Workflow

Severity: High


 * Upstream tasks: https://secure.phabricator.com/T7916 and https://secure.phabricator.com/T5411 --AKlapper (WMF) (talk) 18:02, 25 November 2016 (UTC)

Pholio comments overlay image
In Pholio, users can select a part of a mockup. If the mouse is released after selecting, a comment dialog named "New Inline Comment" pops up. The pop up appears in the middle of the screen and can not be moved. Thus, it often overlays the part you want to comment on.

Kind of: Workflow, Bug

Severity: Medium


 * Upstream tasks: None. Feel free to file one. --AKlapper (WMF) (talk) 18:02, 25 November 2016 (UTC)

Integration of Comments on Images in Issue discussion
When discussing an mockup (from Pholio) or image in an issue of Phabricator, there is no possibility to refer to a certain part of the image. One can comment on a part of a mockup in pholio, but not directly form the issue on phabricator.

Kind of: Workflow, Enhancement

Severity: Medium


 * Upstream tasks: None. I don't see an issue as you are supposed to discuss the mockup in the mockup discussion and not in some associated Maniphest task. If you want to discuss parts of an image, post it as a Pholio mockup instead of as an image file. --AKlapper (WMF) (talk) 18:02, 25 November 2016 (UTC)
 * "supposed to discuss the mockup" Yes – but that does not make it necessarily good (or fitting-for-this-case). I often work closely with developers and often need to consider technical limitations and thus iterate the mockups with them. As far as I understand, we would need to switch back and forth between Maniphest and Pholio than. It may be the case that I can solve the problem by some other means, but I have not found a smooth workflow yet. --Jan Dittrich (WMDE) (talk) 08:25, 28 November 2016 (UTC)