We usually check the storage that we are using once a week and noticed that there was a sudden jump in storage usage (almost 40%). How do we figure out what is using the extra space?
My thoughts would be that someone added a really large attachment to an issue. Or possibly many issues with many large attachments were created that week.
This is not a critical issue as we are nowhere close to the maximum storage, however, I would like to know what caused this.
From reading other posts, it seems that there is no way to query the size of an attachment using JQL.
Is there a way to search when an attachment was added to an issue?
Hi @Abhay
you are correct that you can't query the size of attachments using plain JQL, and to the best of my knowledge, you also can't query for when an attachments have been added.
You might be able to use Jira Automation to write these information into custom fields and then use the custom fields to query your issues, but someone else would have to lean in for the details.
Alternatively, if you're open to solutions from the Atlassian Marketplace, you'll find options there. E.g., my team and I are working on an app in which this would be trivial to do; I'll provide more details below.
Just to expand on the last point, this is how this could look in the app that my team and I are working on, JXL for Jira:
For context, 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 number of so-called smart columns that aren’t natively available, the attachments size.
As you can see above, you can easily sort and filter your issues by the attachments size, and also use it across JXL's advanced features, such as support for configurable issue hierarchies, to issue grouping by any issue field(s), sum-ups, or conditional formatting.
Any questions just let me know,
Best,
Hannes
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.