Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Automation - Delete Issue Not Working Despite Success Status

Jason Campbell
Contributor
April 26, 2021

I've created a workflow that *was* working, but then I began receiving the following message in the Audit despite the Automation showing a Status of Success:

------

Delete issue

Jira was slow to respond. Automation attempted to delete an issue, but the results of the operation are unknown. Most likely it succeeded.

------

I have no idea why this began showing up in the Audit, but ever since it did none  of the issues that were supposed to be deleted were successfully deleted. I'm hoping to delete 10 subtasks, but zero are deleted.

2 answers

1 accepted

1 vote
Answer accepted
John Funk
Community Champion
April 27, 2021

Hi Jason,

Why don't you just transition the sub-tasks to another status instead of deleting them? Maybe like Done if they are Done or Discarded or something like that?

But also, why are you completing a Story and then moving it back to Done with all new Sub-tasks? Why not just close the Story and clone or create a new story with new sub-tasks? 

And just as a side note, it' usually not good practice to delete ANY issue. Especially one that has been worked on, and possibly completed. 

Kevin Johnson
Community Champion
April 27, 2021

@John Funk True and it is not a good practice to bring back a completed story with completed subtasks to the backlog and delete it later.

Like John Funk likes this
Jason Campbell
Contributor
May 4, 2021

I originally planned on going the Clone route, but I was unable to update the Status of the Subtasks in my automation....so I went the Delete route.

After seeing your comment, I revisited my original Clone method and finally figured it out. The solution was to create a second workflow to modify the status of the subtasks created in my Clone automation. It seems like I should be able to both create and modify status in the same automation, but after working w the Jira support team a second workflow was the best we could do.

Like John Funk likes this
0 votes
Kevin Johnson
Community Champion
April 26, 2021

Hi @Jason Campbell ,

Was the automation set up to delete the issue as well as the subtasks?

Cheers, Kevin.

Jason Campbell
Contributor
April 27, 2021

No, the overview of the workflow is:

  1. When Story is transitioned to Done
  2. Update Story Labels, Assignee, Due Date and Reporter
  3. Transition Story to Backlog
  4. Then Delete all Sub-tasks
  5. Then Create four(4) new Sub-tasks
  6. Transition the Sub-tasks to Backlog
  7. Update Sub-task Assignee, Labels and Reporter

All steps work every time except Delete. I've even moved Delete up and down in the process to see if ordering makes any difference.

The part that's driving me crazy is that this process worked for about a week or two before it began to fail....

Kevin Johnson
Community Champion
April 27, 2021

so how is the automation set up to delete the sub-tasks, can you share a picture or explain on that part.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events