Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,361,704
Community Members
 
Community Events
168
Community Groups

Duplicate workflow step cannot be deleted

Edited

Hi,

Somehow we have managed to create a duplicate of a workflow step, with the duplicate completely unlinked from the workflow.  We cannot delete the duplicate.

See attached screenshots showing the duplicate (both in text and as a diagram), and also the error we receive when double-clicking on the workflow step.

Any assistance deleting this step would be appreciated!

Thanks,

Claude.

 

duplicate-workflow-step-text.pngduplicate-workflow-step-diagram.png

1 answer

1 accepted

1 vote
Answer accepted

I think what you might want to try is download the workflow as xml (Export -> xml), then open it and remove the extra step manually, save it, and upload it back as a new workflow, and then replace your original with it.

The extra step will probably look like this:

<workflow>
<name>workflow name</name>
<actions>
<initial-actions>
...
</initial-actions>
<common-actions>
...
</common-actions>
</actions>
<steps>
<step id="31" name="Manual Creation Required">
...
...
</step>
...
</steps>

 

So you can just delete the whole step, look for the id and you'll see it.

Mind you when you try to re-upload the workflow, it might be trying to create new screens or create new custom fields, depending on how that workflow is customized. So you might want to further edit it again, this time in Jira, set back the old screens, and then delete the extra duplicates it created, to keep your system clean. It should give an overview list of what it is about to create - so just to note it down for some house cleaning afterward.

 

If the webUI won't let you modify it, then this is pretty much the only way as far as I can tell. As for how you managed to get a duplicate step in there - I don't recall ever seeing it before, so I don't think it's anything common, one of those mysteries I suppose.

Thanks Radek.  As it happens, we suspect an export/import created the problem.  But you suggestion is a good one.  We will try that at some point.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
TAGS
Community showcase
Published in Jira Service Management

An unofficial way to monitor a JSM mail handler for errors

...eturns true if any content is returned for the webResponse.body.data.first s...

718 views 3 20
Read article

Atlassian Community Events