JIRA Bulk Change won't go to confirmation step

[Burak Kocak]

While using bulk change in JIRA I could not go to confirmation page. When I click the next button nothing happens. Even no log written on logs. The next button act like fake button. This situation in one day without changing any plug-ins. This situtation happens only editing.

JIRA version v6.4.14#64029-sha1:ae256fe)

[Thomas Deiler]

Dear @Burak Kocak,

first of all, you should not use Jira 6.4.14 anymore.

With the information you gave its hard to help. I just can give you some hints that show directions:

• your permissions are not sufficient to continue - check your permissions
• a mixture of different issue types of different projects doesn't allow you to edit a specific field - retry a bulk run on a smaller amount of issues to identify the reason

So long

Thomas 

[Burak Kocak]

Hi @Thomas Deiler, actually this bulk change is needed for upgrading the jira software to 7.9. We try to make a data corrections so hope to have more consistent instance.

Tried with only one issue still nothing happens.

I have rights to make bulk change and the problem is the NEXT button on the operation details step won't work. Even we try in browser console with document.getElementById("next").click() nothing happend.

I think the problem is the customfield  comes from one of the plug-in. But we don't install new plug-in.

By the way thanks for your interest.

[Maree Milne]

Hi Burak

Did you ever resolve this? I am having the same issue trying to update a field from the Group Sign-Off add on, all other bulk updates on the same issues work...

Cheers

Maree

[Burak Kocak]

Hi Maree,

We handled the situtaion with Mozilla Firefox developers tools.

1. Go to bulk change, and select operation edit
2. Press F12 on keyboard to open developers tool
3. Click inspector then html pane
4. on html pane right click and select edit as html
5. Insert a new line with pressing enter
6. Click outside the html pane and it will refresh the page again and next button works for me.

After we upgrade our instance to 7.9 we won't have the problem again.

Cheers

[Maree Milne]

Thanks! Will try this next time we have the problem.