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

Why did my workflow change & why can't I correct it?

JasonSylvester

For some reason, my workflow has been changed, no one knows how/why, and when I try to correct it I get an error message. I cannot figure out how to get Review added back in without continually getting this error message.

Images for original config, missing Review, and adding Review error added. Review error.jpg

Accepted answers

Ashish Bijlwan_zogaqs

Hi @JasonSylvester

Welcome to Atlassian Community!

You can check the Audit Log to know when the workflow was changed.

Audit Log.png

In order to add the Review Status, first create a copy of the workflow, because statuses can't be added or removed from the Active workflow.

You need administrative privileges to copy workflows. Log in to Jira as an administrator.

Go to the "Jira Administration" section and select "Issues" from the menu. Click on "Workflows" to view the list of existing workflows.

Find the workflow you want to copy in the list.
Click on the "Copy" option next to the workflow. This will create a duplicate of the workflow with a new name.

You can now edit the copied workflow to make any necessary changes. This includes modifying statuses, transitions, and other workflow properties.

Once you have made the desired changes, publish the workflow to make it available for use in your projects.
Go to Project - Project settings - Summary -Click on Workflow Scheme
then click on Add workflow - Add existing, a list of existing workflow will appear, look for the one that you copied and modified with necessary changes and click Next - Select the Issue Types - Finish and then click the Publish Button.

Thank you,
Ashish

All comments

Dick

Hi @JasonSylvester Welcome to the Atlassian Community.

At first glance, it appears that someone removed the status "Review" altogether from your project workflow.

Normally, deletion of a status can't be done without first moving affected issues to another project or status or Jira will pipe up with this message:

Status removal message.png

Also, transitions from one workflow to another workflow (one without the Review status) would prompt an administrator with an extensive dialog that serves solely to migrate all individual issue types to the available statuses.

You describe that you're doing something to get "review" back in. The error makes me suspect that you're editing the board and are (re-)placing statuses into columns. Can you elaborate on this, so it's more clear what you're doing prior to the error?

Best regards,

Dick

Ashish Bijlwan_zogaqs

Hi @JasonSylvester

Welcome to Atlassian Community!

You can check the Audit Log to know when the workflow was changed.

Audit Log.png

In order to add the Review Status, first create a copy of the workflow, because statuses can't be added or removed from the Active workflow.

You need administrative privileges to copy workflows. Log in to Jira as an administrator.

Go to the "Jira Administration" section and select "Issues" from the menu. Click on "Workflows" to view the list of existing workflows.

Find the workflow you want to copy in the list.
Click on the "Copy" option next to the workflow. This will create a duplicate of the workflow with a new name.

You can now edit the copied workflow to make any necessary changes. This includes modifying statuses, transitions, and other workflow properties.

Thank you,
Ashish

JasonSylvester

I just set this up last week. Some dummy tickets were added to created the reports, then removed. Why Review was removed, I have no idea.

JasonSylvester

Let me try this tomorrow. By the way, the workflow has no active tickets, as we just set this up and put in some dummy tickets for testing; if that impacts your suggestions for how to correct this.

JasonSylvester

Also, I am not a Jira admin with those privileges, if you can please suggest an alternate way to fix this without having to recreate it again.

Dick

Hi @JasonSylvester ,

If you've set it up, you're the Jira admin...

The above procedure is only necessary when there are more than one project making use of the same workflow that you're using in your project. If that's not the case, just edit the workflow to your hearts content.

Dick

Alexander Stern _ Shern Consulting OÜ

This kind of situation is exactly where things get tricky.

Usually the audit log can confirm that a workflow change happened, but it doesn’t always make it easy to understand what exactly changed or trace it quickly during debugging.

In practice, I’ve seen that once something “unexpected” happens, the investigation part is often the most time-consuming.

Having a focused view of just workflow changes (instead of going through the full audit log) makes it much easier to pinpoint the root cause.

We ran into this enough times that I built a small tool to make this process easier.

Happy to share if still relevant.

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

workflow