This issue has impacted us too. We are heavily relied on labels for our document management and this bug is really bothersome for us.

Dear all,

for those who can't wait (like me): I added a small app to the Marketplace which closes the gap: https://marketplace.atlassian.com/apps/1220787/attachment-boxes?hosting=server&tab=overview. It is open source in case you need to adopt it.

Kind regards Andreas

@Alex Yakovlev would it be at all possible to get some form of transparency on how many votes would be necessary to move this issue up in prioritization channels? At what point does a ticket become highly requested? This issue is crippling any hopes I have for my team's implementation of Confluence, and I've already wasted hours of my program's time manually adding labels to each file I upload. 

I'm afraid we missed our window here.

@Richee: There is no app for this. Also, it is important enough to fix. They did it for the cloud instance.  See https://jira.atlassian.com/browse/CONFCLOUD-53570.

It just didn't make it into the server code base ...

5 years after opening this issue, they are still Gathering impact... And customers still go and pay for Confluence. That means 

• either this is not an important functionality and time has proven that
• or there is a commercial macro, that you can buy to solve this issue, which you can voluntarily buy

Labels are key to our document management process. The inability to assign labels during drag-and-drop makes the attachment macro nearly useless. What is the plan to implement this requirement? What would it take to escalate it above a Low priority? 

We are having the same problem and frustration. Attachment Macro as currently implemented doesn't seem suitable for file management.

Can we please have this issue fixed?  I'm having difficulty engaging our users in using Confluence for file management due to not being able to easily categorise attachments on a single page. 

I can also confirm that this issue is present in 6.14. I'll echo what others have said, this feature is near essential for our use-case for Confluence Server. 

We are currently testing out Confluence Server 6.12 and can also confirm that the issue still exists, this functionality would be vital for my company and I was wondering if anyone had an update?