+8
Planned

As a user I would like to add attachements to stories in order to have all the information necessary to complete a story

rawedge 6 years ago • updated by Matthew O'Riordan (Founder) 3 years ago 5

Each story should allow attachments to be added to it. 

This would allow us to ensure our wireframes and designs as well as final design assets are up to date and with the story when a developer takes on the work

Answer

Answer
Planned

Thanks for the suggestion.  This is something we have considered, but have not pushed this feature through yet as because we are not charging our customers, the storage costs could become problematic for us.  When we find a solution, we'll update this ticket though.


Thanks again, and in the mean time could you not link to your attachments on a 3rd party service from the comments fields?

Answer
Planned

Thanks for the suggestion.  This is something we have considered, but have not pushed this feature through yet as because we are not charging our customers, the storage costs could become problematic for us.  When we find a solution, we'll update this ticket though.


Thanks again, and in the mean time could you not link to your attachments on a 3rd party service from the comments fields?

I have been using google docs with a pointer as a solution, but it presents a problem when my client doesn't have a google account. Having a consistent location would be good. I could see and understand where this would present a space problem, maybe space constraints on the item?
We are considering a paid option, so we could cope with storage issues if we have revenue to support it.

How about providing functionality to FTP documents to a private FTP server. You could configure the credentials in the project settings and then when you want to upload/attach a document to your scorecard the system will simply upload the data to the private FTP site and link to it to download it again via the URL that will be created. Alternatively the FTP site needs to be exposed via Http or something like that... Thus the storage of the documents will be on a private server not utilizing space on the systems infrastructure.

It's a nice idea, but Basecamp many years ago abandoned that approach due to the complexity of problems with 3rd party FTP servers, and also the fact that FTP is dying in terms of use these days.