See https://secure.phabricator.com/T4655#20 for discussion.

To clear, having inline attachments is very nice and should not change. This task is about the fact that because their are inline, they end up being hidden as well as the comments, while arguably, attachments are distinct from comments and for some tasks more important and should remain easily accessible.

Can you explain your use case a bit more? The general 'list all things attached to comments' seems not useful 95% of the time. If there is a specific case, like design progress, it might make sense to solve that differently (like through Pholio).

For example, if I update the design of an item on a task, it would be useful to either use Pholio to thoroughly track mock progress or for simple things update the Description of the task itself for the latest design.

Pholio is in beta though, so should we really be using it?

Pholio is definitely usable, at least worth testing for your needs. It is a little rough still on the UI side and policies are not yet implemented, but otherwise works as expected.

That might solve our need indeed, so we'll try it. Feel free to close this task.

For context, here's a comment from our designer:

the main use case for me would be attaching mockups and assets for a developer to implement. When I hand off a task to Sam or whomever, they have to comb down the change log to find attachments inline, but it seems like it’d make more sense to have them arrayed at the top of the task as well.

We're going to be quite happy with Pholio, you can close this task. Thanks!

Well since you asked for it: T5359: Improve handling of non-supported image types in Pholio. That's the first issue we hit after introducing to our designers (not a blocker but annoying and probably not hard to fix).