Opened 18 years ago
Closed 18 years ago
#4161 closed enhancement (wontfix)
New ticket w/attachment in 1 step
Reported by: | Owned by: | Jonas Borgström | |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | ticket system | Version: | 0.10 |
Severity: | normal | Keywords: | |
Cc: | eli.carter@… | Branch: | |
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
I'm looking at writing a screenshot utility that would feed Trac's newticket form. The syntax for putting initial values in various fields by using the URL is great, but I'd like to be able to do the same thing for attachments.
The "I have files to attach to this ticket" checkbox implemented for #588 is a step in the right direction, but I don't think that takes it far enough.
Uploading the attachments on preview to a "holding area" is quite acceptable for my purposes. Based on the #588 discussion, I understand this may be is difficult to implement, but I believe this would significantly improve interaction with Trac.
Attachments (0)
Change History (2)
comment:1 by , 18 years ago
Type: | defect → enhancement |
---|
comment:2 by , 18 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
I agree with mgood, and propose a wontfix resolution here.
Your utility won't be able to pre-populate an attachment field since browsers protect file upload fields from being pre-populated for security reasons. You may want to look at using the XmlRpcPlugin since it provides functions for creating new tickets and attaching files to tickets, so your utility could automate the entire process.
I think that making multiple attachments easier (as suggested in #2141) will make the attachment process better. I'll leave this ticket open for now for feedback, but I feel like adding an attachment field at ticket creation makes only a small difference in usability which doesn't really justify the problems and complexity introduced to deal with orphaned files.