How to bulk upload different values

Question

Hi All ..

I'm aware of how to update one value(one Label) in multiple EPICs in bulk upload ..

I have a scenario like :

I have 50 Unique Labels(Label 1, Label 2 .. Label 50)

All these have to updated in 50 different EPICS (Existing EPICS)

like

Label 1 in existing Epic 1

Label 2 in existing Epic 2

.

Label 50 in existing Epic 50

Is there a way to do it in bulk !!??

OR

is there a way to do it through JQL ??!!

Hannes Obweger - JXL for Jira · Answer

Hi @Ramu

if you're open to solutions from the Atlassian Marketplace, you may want to have a look at the app that my team and I are working on, JXL for Jira.

JXL is a full-fledged spreadsheet/table view for your issues that allows viewing, inline-editing, sorting, and filtering by all your issue fields, much like you’d do in e.g. Excel or Google Sheets. It also comes with a long list of advanced features, including the ability to bulk edit your fields using copy/paste. This works within JXL, but also between JXL and pretty much any other tool, including e.g. Excel or Google Sheets.

So what you could do is to open your data in e.g. Excel, and simply copy/paste the values over, like so:

I'm using story points here, but it would work the same way for any other issue field(s). You don't actually need the issue key; you just want to make sure that you paste into the correct set of issues.

Just be aware that JXL's copy/paste logic currently replaces the existing labels, rather than adding to them. If it's the latter that you're looking for, I can advice on this, too.

I should also add that JXL can do much more than the above: From support for configurable issue hierarchies, to issue grouping by any issue field(s), sum-ups, or conditional formatting.

Any questions just let me know,

Best,

Hannes

Marc -Devoteam- · Answer

Hi @Ramu

There is no JQL for this.

The only option is CSV import, to update your issues.

In you CSV specify the issue keys also in a column, so the exiting issues will be updated.

Ramu_kd54ib · Answer

Hi Aaron,

To avoid any such incorrect csv scenarios .. what i did was .. first i extracted few of the existing EPICs as a csv file ... Then tried importing the same csv with the new labels (Label 1 .. Label50) in the csv updated.

and the validation (Validate ..before 'Begin Import') was perfectly fine .. so it is all fine with csv template and fields ..

for the 'Issue Key' field, in the drop down there was no exact match like Issue Key available and i couldn't map it .. this resulted in i end up creating new Tickets instead of updating the existing ones !!

i have standard level of Admin access otherwise, i couldve done this via JIRA administration/system settings/external import ...

(but getting that level Admin access is not possible in the org where i work)

Even ..tried from JQL perspective of trying to update the existing Label like change/update/amend/append Label but as you are aware , none of these are available/possible in JQL .. ()

so, concluding all these tried my luck of checking here to see any workaround or alternate option/thoughts ..