Stop a hung Bulk Edit

David Hogan September 27, 2018

Is there a good way to stop a Bulk Edit Operation in progress without bouncing the server?

Bulk operation is 0% complete after over a day.

 

4 answers

1 accepted

3 votes
Answer accepted
KellyW
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
September 27, 2018

Hi David,

 

Following suggestion needs to be run by the user who executed the task. In addition the user must be a JIRA Administrator in order to delete the task.

  • If necessary grant temporary admin permission, delete task, then remove admin permission.
  • URL below applies to bulk edits as well as project changes:

    There is a internal REST point to stop tasks:

    • DELETE /rest/projectconfig/1/migrationStatus/#id
    • "#id" can be taken from the progress page's URL.URL below applies to bulk edits as well as project changes
David Hogan October 1, 2018

Thanks, Kelly

David Hogan October 4, 2018

Kelly - Once I got the correct URL structure, it worked perfectly. Thanks!

Joseph Chung Yin
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 29, 2019

Hi David and Kelly:

What will be the correct URL for stopping a buld edits action -

Example our bulkedit url was - 

https://jira.abc.com/secure/views/bulkedit/BulkOperationProgress.jspa?taskId=48321

Best, Joseph Chung Yin

Like Allan Nunez likes this
David Hogan May 1, 2019

Hi Joseph -

Leveraging Postman, available at https://www.getpostman.com/, send a DELETE request to the following https://jira.abc.com/rest/projectconfig/1/migrationStatus/48321

You'll need to configure Authorization leveraging your JIRA username and password.

Good luck!

Like # people like this
3 votes
Joseph Chung Yin
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 1, 2019

After further analysis.  Here is the answers (Bulk Edit or Project Changes Activities) -

Extracting some original answers from Atlassian's response -

1) Grant user who initiated the stuck bulk update job with Jira Administrator right

2) Open COMMAND line window on your user's machine and execute the following curl command - 

curl -k -XDELETE -u <USERID> https://jira.xyz.com/rest/projectconfig/1/migrationStatus/<TaskJOBID>


2a) Replacing the USERID with the user account and apply the TaskJOBID.


3) Ask user to conduct bulk update action again once the curl command is successfully executed.

4) Revoke the temporary Jira Administrator right

 

Hope this helps.

Best, Joseph Chung Yin.

Bridy Frett June 24, 2019

We tried the CURL command supplied with Jira v7.13.2, but received the following error:

'DEPRECATED JS - contextPath global variable has been deprecated since 7.4.0. Use `wrm/context-path` module instead.'

Bridy Frett June 24, 2019

Ah, we were able to get it working using postman.  Thanks for the tips!

Anil Mishra April 19, 2021

Can't directly admin run this delete api? 

I tried with admin but its throwing 403 error.

 

Thanks,

Anil

Like # people like this
0 votes
Vinnie Chhabra March 4, 2021

Thanks for this helpful information.   How can I find the TaskJOBID. of a user's bulk request?

The user doesn't know it.

Dave Liao
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
October 27, 2021

@Vinnie Chhabra - I think you can have the user re-attempt a bulk operation. They should be re-sent to their last-run task - if that happens, have them copy the URL, and the taskId should be at the end of the URL.

0 votes
Allan Nunez May 1, 2019

Ditto to Joseph's Question.

Suggest an answer

Log in or Sign up to answer