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; } } }

Corrupted Default Workflow

David Liechti

Somehow I managed to edit the Jira default workflow, which should not be editable. How can I restore that workflow?

When defining a custom workflow my own transissions aren't available on the issue sites. They are still called as they are in the default workflow (Close, Resolve Issue). I assume that's because of the corrupted default workflow...

Thanks for any help!

Accepted answers

AlaA

Hey Dave,

I think you can import the default classic workflow from marketplace to your JIRA instance. Here is the link:

https://marketplace.atlassian.com/plugins/com.atlassian.workflow.bundles.classicdefault

I hope that help.

All comments

AlaA

Hey Dave,

I think you can import the default classic workflow from marketplace to your JIRA instance. Here is the link:

https://marketplace.atlassian.com/plugins/com.atlassian.workflow.bundles.classicdefault

I hope that help.

David Liechti

Thanks! I already got an answer from the JIRA support regarding the second issue:

Hi David,

Thanks for writing to us. Regarding your issue, refer to following points below:

1. Currently, It is NOT possible to set other workflow to be default OR edit / delete the existing default workflow. There is a feature request for this, you can have a look and vote for it at: https://jira.atlassian.com/browse/JRA-9363 . In order to be implemented, it must meet certain levels according to ourimplementation of new features policy

2. The transition issue has been fixed on TEST-13 ticket. There are 3 options Close, Start Implementation and Analyze located under Workflow button. The issue is related to a known bug in JIRA: https://jira.atlassian.com/browse/JRA-29546 . As you have changed Resolve Issue to Analyze but the transition-idnumber still same. To fix this, we have deleted the old transition and add a new one with same name to change this number. The bug is currently verified by our development team. In order to be fixed, it must meet certain levels according to our bug fixing policy.

Regards
Steven

AlaA

Dave,

That's wonderful.

I'm glad that our support team was able to assist you regarding this.

Have a good weekend ahead.

Cheers,

Kamel Boulos

Hi Dave,

I'm experiencing the same issue where somehow I managed to edit Jira default workflow. I've tried to import the default classic workflow from marketplace, but no luck. How were you able to restore the Jira default workflow?

Thank you,

--Lucky

Kamel Boulos

Hi Dave,

Thank you so much for your quick reply. I will give it try.

Have a great day! :-)

--Lucky

David Liechti

Hi Lucky

The issue was in the end solved by the Atlassian support. I got the following answer from them:

"The issue is related to a known bug in JIRA: https://jira.atlassian.com/browse/JRA-29546. As you have changed Resolve Issue to Analyze but the transition-idnumber still same. To fix this, we have deleted the old transition and add a new one with same name to change this number. The bug is currently verified by our development team. In order to be fixed, it must meet certain levels according to our bug fixing policy."

Cheers

David

Welcome!

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

Quick Links

Find more posts tagged with

jira

transition

workflow

default

button