Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

attachment as custom field


is there any way I can create a custom field, like "install guide" that is an "attachment" type?

From what I see attachment is a general concept and there is no way to use this as a specific field. This makes it difficult to identify different documents within a issues. One always has to use the document name. It would be great that a custom "attachment" field would exist and that one can refer to this custom field in comments and such.

Anyone has any idea if this is possible?



7 answers

Agreed - The ability to create a custom field of type "Single Attachment (Versioned)" specifically for one standardized document would be immesely helpful.

For example, in our standard New Feature ticket, I would add:

Business Requirements Document (BRD) ________________

Quality Assurance Test Script ________________

Project Plan _________________

Techinical Design Document (TDD) _________________

High Level Design Document (HLD) _________________

Peer Code Review Checklist _________________

Unit Testing Artifacts ________________

QA Testing Artifacts ________________

UAT Testing Artifacts ________________

Release Notes _________________

These are all standard documents which must be attached prior to feature release, and for which we have no desire to embed Wiki-style directly in the ticket. A URL link to a Wiki page will not suffice - the Wiki markup is too high a barrier to entry for our large team of varying technical prowess.

I envision that each of these fields would accept only a single attachment, but that the document can be auto-versioned by re-uploading a document of the same name. Prior versions of the document could be accessed via an expanding and indented tree, similar to the treatment of .zip files today.

There could also be a type "Single Attachment (Non-Versioned) if there is a desire to prevent the storage of the document version history.

A "URL Field" type customfield can be used, filled with the url of the attachment. If you specify the features of the "attachment" type customefield it could be developed as a new customfield plugin.

We recently published Apwide File Field that should cover your need. 

Is there a plan to roll out a version for cloud?

Like # people like this

Hi Nathalie, thanks for your interest for a cloud version. We will implement a cloud version of the app on it as soon as we get more requests for it!

Like Guillaume likes this

@David Berclaz how close are you to rolling out a Cloud version of your add-on? We're using Jira Cloud and have a real need for this feature.

Like Guillaume likes this

we need a cloud version!

Like # people like this

Hello @Fred Smith & @simon,

I just created the feature request, could you vote for it if you still have the need of having a cloud version of Apwide File Field?

#9 Deliver a version of Apwide File Field for Jira Cloud

Thanks in advance.


I know I am late to the party but we also need this feature for our jira cloud. Looking forward to it

Like David Berclaz likes this

Hi @kan fuzed

Sure, we'll update this topic once delivered.
Don't forget to vote on the ticket if not done already.


Same here, that field for cloud will be great, im voting

Like David Berclaz likes this

@David BerclazI can't vote on the issue, but throwing in another request for Jira Cloud.

Like David Berclaz likes this

I'm not able to vote on the issue, but also adding another request for Jira Cloud.

Like David Berclaz likes this

Hi @David Berclaz 

so, this Cloud version was abandoned? :c

The intent here is slightly different.

In the same way Reports and Assignees are two different defined fields, but they are both of type "People" with a standardized interface...


We also have a need for different (custom) fields of "Business Requirements Document" and "Quality Assurance Test Script", with a common document upload and file versioning interface. It would render identically to the generic "Attachments" field, but could be labeled with greater specificity. 

This would alleviate the need for enforcing file naming conventions and file versioning conventions across multiple teams and team members.  I don't care what you call the document, as long as you upload it under the "Business Requirements Document" attachment field.  I don't care what you name the wireframes file, as long as you upload it under the "Wireframes Document" field.

This is especially powerful if we separate development, qa and deployment concerns on separate tabs.

Today, there is no "attachment" field type - We can only reference the generic bucket of attachments buried somewhere in the comments.

Another way of saying it is that "Watchers" (just a generic bucket of people) are to "Attachments" (a generic bucket of files) as "Reporter" (a specific defined person) is to "Business Requirements Document" (a specific type of document.) and "Assignee" (a specific defined person) is to "Mockups Document" (a specific type of document.)

Permitting "attachment(s)" as a *custom* field type would allow the end user specify the document types that best align with their process (and ticket types.) 

The previous comments are exactly one of the requirements that I have for a work request system that I am working on. We are currently evaluating capabilities of various COTS suppliers. 

Just to make sure you can refer to any attachment from the comment as it is document at In case the type of the attachment allows it also can be embedded into the comment as well and

Is there any plan to roll this out for jira cloud? 

It's a type of function that cannot be implemented in Cloud, unless you take the attachment storage out to a 3rd party.

Suggest an answer

Log in or Sign up to answer

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you