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?
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.
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.)
Just to make sure you can refer to any attachment from the comment as it is document at https://verhas.atlassian.net/secure/WikiRendererHelpAction.jspa?section=links. In case the type of the attachment allows it also can be embedded into the comment as well https://verhas.atlassian.net/secure/WikiRendererHelpAction.jspa?section=attachments and https://verhas.atlassian.net/secure/WikiRendererHelpAction.jspa?section=images
take a look at https://marketplace.atlassian.com/plugins/com.stiltsoft.jira.smart-attachments/server/overview?_ga=2.132382474.543781189.1506343677-1477250590.1492612748 ... you can define attachment categories and manage access permissions
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?
Thanks in advance.
Hey admins! I’m Dave, Principal Product Manager here at Atlassian working on our cloud platform and security products. Cloud security is a moving target. As you adopt more products, employees consta...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs