342811 - Add a page for bulk loading components

Status: NEW

(Bugzilla :: Administration, task)

Description

[Andrew Stadler]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.4) Gecko/20060614 Fedora/1.5.0.4-1.2.fc5 Firefox/1.5.0.4
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.4) Gecko/20060614 Fedora/1.5.0.4-1.2.fc5 Firefox/1.5.0.4

Adding components to a product takes a whole lotta' clicking.  It would be great if you could provide a page for entering bulk components on a new product.  A simple series of boxes in a grid would suffice.  Name, description, default assignee.  Maybe 10 or so rows and a single commit button.

Reproducible: Always

Steps to Reproduce:
1.  Create new product
2.  Go through steps of adding 10 components to it
3.

Comment 1

[Brian Biales]

I agree, but let's not stop at components.  You can do this adding users, adding products (granted there are much fewer products to add than components).  But you could edit the list of versions this way, keywords, really any place you have list of items...

Comment 2

[Simon Green]

(In reply to Brian Biales from comment #1)
> I agree, but let's not stop at components.  You can do this adding users,
> adding products (granted there are much fewer products to add than
> components).  But you could edit the list of versions this way, keywords,
> really any place you have list of items...

There are other bugs for bulk adding of other records (like version, milestones, users, etc), so I will focus on just components for this bug. If there are any record types that are missing, we can created a new bug for them.

Here is what I propose:

1) There is a new section in the admin menu for bulk uploads. It will have a drop down with the different types of records that can be uploaded (currently only components, but will more will be added later). There will also be a link from the appropriate section of the current admin pages to the bulk upload page.
2) The page will specify what columns must be specified (which vary on what type of record been uploaded), which are optional, and which can have multiple values.
3) The user will upload a CSV file. The first row will be headers that must match exactly the column names in step 2. If a column supports multiple values (e.g. default_cc), then that can be a header in multiple columns in the CSV file.
4) The CSV file is processed.
 a) If there are any mandatory headings that are missing, the process will fail
 b) If there are any headings that are not recognised, the process will fail
 c) If any row cannot be processed (e.g. invalid e-mail address for the default assignee, the component name already exists for the product, or the component name is too long), no records will be processed.
...
6) Profit :)

Using a CSV file is a better solution than multiple rows with select boxes since the file can be checked by various people before the data is entered.

Comment 3

[Dylan Hardison [:dylan] (he/him)]

I hope you're planning on using Text::CSV preferred. :)

Comment 4

[Dylan Hardison [:dylan] (he/him)]

s/ preferred//

Comment 5

[Simon Green]

Attachment: v1 patch