Jira filter to count the number of attachments

Question

Hello,

There is this new Jira update that a ticket cannot contain more than 15 attachments, or the overall size limit is not exceeding 100 MB.

Is there any Jira filter that can count how many attachments are in a ticket and highlight those that are exceeding the number?

Thanks!

Inna S · Answer

Hi @Charlotte Santos -Appfire-

the count is wrong on our site:

* when there are no attachments it says there is 1.0. Yes, with a decimal point.
* when there is 1 attachment it says there is 0
* when there are more than 1 attachments, the number they display is X-1

Looks like you start counting from zero from the first attachment.

Naturally, when you remove all attachments you get to -1, and then appear to take the modulus of it to arrive at '1'.

This is totally messed.

Charlotte Santos -Appfire- · Answer

Hi @Nicoleta Burz

I’m Charlotte, a support engineer at Appfire, and I’m here to help you.

Sadly, natively, you’ll not be able to count attachments in an issue.

However, in the app where my team works, JQL Search Extensions for Jira, you can use the query below to find all issues with more than 15 attachments:

attachmentsCount > 15

Please contact our support if you have any other questions about this query.

We’ll be happy to help you! 😉

Hannes Obweger - JXL for Jira · Answer

Hi @Nicoleta Burz

welcome to the community!

If you're open to solutions from the Atlassian Marketplace, this would be easy to do with the app that my team is working on, JXL for Jira.

JXL is a full-fledged spreadsheet/table view for your issues that allows viewing, inline-editing, sorting, and filtering by all your issue fields, much like you’d do in e.g. Excel or Google Sheets.  It also comes with a long list of so-called smart columns that aren’t natively available, including the number of attachments, the attachments size, and several more attachments-related columns.

This is how it looks in action:

As you can see above, you can easily sort and filter by your smart columns; you can also use them across JXL's advanced features, such as support for (configurable) issue hierarchies, issue grouping by any issue field(s), sum-ups, or conditional formatting.

This all just works - so there's no scripting or automation whatsoever required.

Any questions just let me know,

Best,

Hannes