Upload screenshots

#51 Reported over 5 years ago by Robin Corps (Project member)

It would be utterly ace (and actually useful) if there was a feature to attach a screenshot to a bug (and possibly to comments on a bug).


Discussion and changes

Post a comment
Over 3 years ago
Ted Han assigned this to Ted Han
Over 5 years ago
Dan Glegg (Project owner)

Hi Dan – this feature is definitely coming in a big way. But it’ll likely arrive after launch as we’re trying to go live with the bare minimum of features to allow the software to evolve naturally. Some things we want to know are:

  • Do people want to store their information with us?
  • Do people only want to upload images?

Something that is clear is that files will definitely be a child object of a ticket rather than a seperate object a la basecamp.

Over 5 years ago
Dan Zambonini (Participant)

I just want to second (or third?) this.

We often have customers who need to attach screenshots of javascript errors (which can’t be easily copy and pasted), or similar. Similarly, and ‘UI’ based bugs are really hard to describe/track down without an accompanying screenshot.

I realise cost/resource is an issue when you introduce this. I guess you could have a max file size per upload (e.g. 100kb), plus a max storage space per account (possibly dependant on type of package paid for). You may also be able to remove files (or archive/compress them?) as tasks are completed?

Over 5 years ago
Dan Glegg (Project owner)

It’s hard for me to justify including a feature because it’s useful for something Tails isn’t really meant for – but I do also want this feature.

Right now you can include images by wrapping the path in exclamation marks, like so but without the spaces:

! /path_to_my/image.gif !

Over 5 years ago
Tom van de Velde (Participant)

Not sure what that Basecamp SFTP mambo-jimbo entails, but yeah, I just thought I’d say that I’d love a feature like this.
I use Tails as a project managment app, rather than a bugtracking app. If my boss can attach screenshots of little bits of a website that he’s not entirely happy with, it would save him a lot of time, I’m sure. And it could save me a lot of guessing – half the time I need to go back to him to explain again. Sometimes, pictures > words!

Over 5 years ago
Lech Deregowski (Participant)

I was just about to suggest the same, and would say possibly to do this but limit it per account type. Assign either a global storage limit per project or account based on that project or per user, that’s entirely up to you. But this would be very useful for patch and diff files which wouldn’t look pretty or be helpful after pasting into these comment boxes. Either way, some type of storage would be a bonus.

In addition, adding an expiration for those files globally or per user would be optional so they could get cleaned out if space is a concern.

Over 5 years ago
Dan Glegg assigned this to Dan Glegg
Over 5 years ago
Dan Glegg changed status to On hold
Over 5 years ago
Dan Glegg changed rating to TrivialMinorModerateSeverity_star_tiny_inactiveSeverity_star_tiny_inactive
Over 5 years ago
Dan Glegg (Project owner)

I’m working on the politics of this – I definitely want the feature in, but should I provide storage space or should I provide SFTP functionality similar to basecamp?

I’m kinda verging on SFTP because frankly, I don’t want to get into the whole storing multimedia content thing.

Over 5 years ago
Robin Corps created this

Terms of Service Privacy policy Report a problem with the bugtracker