|
Exactly that was my intention.
I like this idea.
So, dear mates at atlassian, what do you think? I think this is possible to implement as a custom field. The attachment would still need to be stored/viewed in the regular attachments list, but the field could have a direct link to "it's" attachment, and the attachment could be set when editing the field.
Hello Jeff,
so you mean that is it not possible to show the attached files "RFP", "Requirements Spec", etc. in the issue view like other custom fields in seperate fields. See JRA 4737 FileMgt_2.gif for details. Showing files at the issue tab would be nice but not necessary. Regards, > so you mean that is it not possible to show the attached files "RFP", "Requirements Spec", etc. in the issue view like other custom fields in seperate fields.
Not currently, but it would be possible with an attachment custom field, which is the subject of this issue. > See JRA-4737 FileMgt_2.gif for details. Showing files at the issue tab would be nice but not necessary. You could actually format these attachment custom fields in a tab, but that would be a separate task: Hi Jeff,
thanx for your fast help. So I can implement this. CU, ---- [ http://jira.atlassian.com/browse/JRA-4925?page=comments#action_26632 Jeff Turner commented on JRA-4925: Not currently, but it would be possible with an attachment custom field, which is the subject of this issue. You could actually format these attachment custom fields in a tab, but that would be a separate task: – Hello Jeff,
could you please give me a short instruction how do I have to use the atlassian-plugin.xml file My first atempt looks like this, but class of the customfield-type-tag has to implement the class com.atlassian.jira.issue.customfields.CustomFieldType <atlassian-plugin key="com.atlassian.jira.plugin.customfield.attachment" name="JIRA Customfields Attachment Plugin"> <customfield-type key="attachmentfield" name="Named Attachment Field" </atlassian-plugin> Markus,
I'm not sure exactly which bit you need help with, but I'm going to assume you need help implementing the CustomFieldType interface. Basically there are a few Abstract classes that you can extend. The ones most pertinent for you would probably be the AbstractSingleFieldType. If you haven't already have a look at: & especially the API for customfieldtype at: You should also think about how your attachments will be stored and what your custom fields methods will do. ie. A text CF stores a string of information. Will the attachment CF store the path to the attachment? How will updating work? How will you delete etc. Hello Mark,
the workaround should be similar to the existing file management: How works the Jira standard file manager? Thanks for your help. Regards, Markus, Do you have the JIRA source release? If so, the source for the DefaultAttachmentManager is in atlassian-jira-enterprise-3.0.2-source\jira\src\java\com\atlassian\jira\issue\managers. Basically the createAttachment method creates a row in the Attachment table and then saves the file to the default attachments folder. Hello Mark, - - - - Regards Markus,
Once you purchase a JIRA licence, you'll have access to the source distribution. This will make extending and customizing JIRA a far simpler task. Basically Attachment class is a bean holding the information about the file (location, name, size). DefaultAttachmentManager is an implementation of the Interface AttachmentManager. The key signature you're concerned with is: public ChangeItemBean createAttachment(File file, String filename, String contentType, User remoteUser, GenericValue issue) throws AttachmentException, GenericEntityException Hello,
where can I get the java file of an ordinary custom field plugin like: "Text Field (< 255 characters) (textfield)" I think it would be a big step to understand the standard custom field implementation. Look at the file 'system-customfieldtypes-plugin.xml' for all the details about the existing custom fields.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
-Technical Concept
-Test Cases
I think this can be useful.