nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Automation - Delete Issue Not Working Despite Success Status

Jason Campbell

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.

Accepted answers

John Funk

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.

All comments

Kevin Johnson_3sxc8m

Hi @Jason Campbell ,

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

Cheers, Kevin.

Jason Campbell

No, the overview of the workflow is:

When Story is transitioned to Done
Update Story Labels, Assignee, Due Date and Reporter
Transition Story to Backlog
Then Delete all Sub-tasks
Then Create four(4) new Sub-tasks
Transition the Sub-tasks to Backlog
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_3sxc8m

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

John Funk

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_3sxc8m

@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.

Jason Campbell

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.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud

automation