Open Bug 278469 Opened 20 years ago Updated 5 months ago

Creating several/multiple attachments in one step

Categories

(Bugzilla :: Attachments & Requests, enhancement, P2)

2.17.7
enhancement

Tracking

()

People

(Reporter: cb13, Unassigned)

References

Details

(Keywords: bmo-ux)

Quite often I have to attach several files to a bug to make it easily
reproducable for the developers. The ability to add several attachments to one
bug at a time would increase the usability

From the gui point of view, there is enough space left on
attachment.cgi?action=enter for at least a second input-set (File, Description
and Content Type). Obsoletes and comments need not to be dublicated.
Or we could use a clone of the Gmail interface for that.
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows 2000 → All
Hardware: PC → All
Assignee: myk → attach-and-request
While both CREATING and EDITING a bug....

Priority: -- → P2
IMHO, there seems to be no reason not to follow the lead of other software interfaces which allow multiple attachements to be entered at one time.  Since the mechanism is obviously in place, it should be relatively easy to fix the interface.

Thanks.
Yeah, along with the option to *not* CC anyone. (if, for instance, you've just posted a comment)
(In reply to comment #7)
> Yeah, along with the option to *not* CC anyone. (if, for instance, you've just
> posted a comment)

Change your personal e-mail settings to stop receiving emails whenever a comment is posted among others. You find it under Preferences.
I'm working on this capability at Yahoo!, my preliminary notion is to put a comma-separated list of attach_id in longdescs.extra_data.
(In reply to KitchM from comment #6)
> IMHO, there seems to be no reason not to follow the lead of other software
> interfaces which allow multiple attachements to be entered at one time. 
> Since the mechanism is obviously in place, it should be relatively easy to
> fix the interface.

It's not that simple. All fields besides the Obsoletes section need to be duplicated, making the UI pretty complex with a few attachments already.
@Fredric B.,
You'll need to explain some things to us.  What is the "Obsoletes" section?

Can't a programmer use a simply loop function to handle multiple items without duplicating the code or causing a complex UI?  The UI portion would be a simple list of entries for the loop to step thru.
(In reply to KitchM from comment #12)
> @Fredric B.,
> You'll need to explain some things to us.  What is the "Obsoletes" section?

When a bug already has some attachments, the "create new attachment" page lets you mark these existing attachments as obsolete.


> Can't a programmer use a simply loop function to handle multiple items
> without duplicating the code or causing a complex UI?  The UI portion would
> be a simple list of entries for the loop to step thru.

There are two cases to consider:

a) either we want a single page from where we can attach as many files at once as we want, or
b) we want a page from where we can attach one file only, and this page is redisplayed again and again till all desired files are attached.

b) is mosty what we have currently, i.e. once a file is attached, you can click the "add another attachment" link to have the same page displayed again. The advantage if this solution is that the UI remains simple and is focused on one attachment at once.

a) is not hard to implement, from a code point of view. It's only a few lines of JavaScript to duplicate relevant fields in the UI when clicking a "add another attachment" link or button, and a loop in Attachment.pm to process each attachment one by one. The complexity is about how to display all these fields nicely. If people consider that the current UI for the whining system is nice, then this is easy to implement. ;)
Summary: Creating several attachments in one step → Creating several/multiple attachments in one step
Do any of the other leading brands have this problem? How could the mighty Bugzilla lack this?
A couple points as I re-read this.  First, I believe that #7 was about a per bug basis, not global.

Second, I also believe that the thinking here is not made very clear with regard to the programming.  If the listing of attachments is simply adding another space as one would add space for another comment, then #11 and #13 appear to be unnecessarily complex.

Third, if that is so, then adding one attachment at a time or a dozen at once should not make any difference at all.  They simply appear as successive entries.
By "leading brands" I meant other bugtrackers.
(In reply to Frédéric Buclin from comment #13)

Implementation ideas:

1) if the browser supports it, have a drop area so you can drag and drop the files onto it.  Each file dropped would create a file field (styled nicely) listing the file to be uploaded.  If not, do the button to add another File field as suggested above, with the browse buttons to pick the file.
2) The parts that are globally affective (obsoletes, take bug, etc) should only be there once, and be processed along with the first attachment (or prior to dealing with attachments) when the form is submitted.
3) All of the attachment-specific stuff can be added to the file fields as they get added to the page, no matter which method of selecting files is done.

It occurs to me that "Add several attachments at once" could be processed the same was "change several bugs at once" is in process_bug.  i.e. handling multiple items becomes the default operation in the cgi that handles the submission, and the case of operating on a single attachment is just a list of one attachment to process (just like making changes to a single bug from that bug's page calls the same code that the change-multiple calls from the buglist page).
(and I think some of that lines up with what you already said up there, I'm just saying it in a way that feels more clear to me)
WTF after 13 years, still nothing??

EVERY other bug reporting website I've ever seen has this!
Hey I'll work on this in Q1 or Q2 2018. https://twitter.com/BugzillaUX/status/935004276170067968
Keywords: bmo-ux
See Also: → bmo_livecoding2

GitHub offers this feature via Markdown.

before the picture

![grafik](https://user-images.githubusercontent.com/73715071/189439422-3dc2eeb1-c602-4464-a0cf-bd51e98aed5a.png)

after the picture

here comes another picture:
![grafik](https://user-images.githubusercontent.com/73715071/189439474-e3d0082e-6437-4480-9f64-08fd93d1892a.png)

And another one!
![grafik](https://user-images.githubusercontent.com/73715071/189439474-e3d0082e-6437-4480-9f64-08fd93d1892a.png)

Refers to https://stackoverflow.com/questions/4779582/markdown-and-including-multiple-files/

Is this still not available? :( Reporting bugs is really difficult without proper attachments.

You can do attachments, just only one at a time.
Letting you do more than one at once is the point of this feature request.

You need to log in before you can comment on or make changes to this bug.