Why is my validator still required after I deleted it?

[Aaron Andrade]

We had a required validator that had to be checked for the approval process to continue. We needed to change some options and we got rid of the other validator. Now we can't move forward with approval process because it tells us we need to check the box. There are no boxes to check and no validator. 

[Brant Schroeder · Accepted solution]

@Aaron Andrade 

It looks like you removed the field from the screen but you need to remove the validator from the workflow.  Check the transition on the workflow to ensure that the validator does not exist on that specific transition.  

[Aaron Andrade]

@Brant Schroeder 

Before I even removed the fields from the screen I made sure to delete the validator. I have looked through the whole workflow and cannot find anything about the EMP local backup. I don't know where to go from here.

[Brant Schroeder]

Does the project have multiple workflows associated with it?

[Aaron Andrade]

yes it does.

[Brant Schroeder]

@Aaron Andrade I have seen it where projects with multiple workflows have updated one workflow that has the requirement but not the other.  Can you check the issue type of the Jira issue having the requirement and ensure that the workflow it is using has been updated?  

[Aaron Andrade]

Checking the other workflows now.

[Aaron Andrade]

@Brant Schroeder Sorry for late response, but I had to finish up some other work. I went through all of the workflows and the EMP Local Backup was no where to be found. We even did a re-index to see if that would help and we still get the error.

[Brant Schroeder]

If the field is not required it has to be on a workflow transition.  Can you share a screenshot of the workflow scheme on the project?  Also what type of project is this, software?

[Aaron Andrade]

Project is for our HR staff to setup new employees and release employees and other functions for employees. Do you want a screen shot of all the workflows opened up or just a shot of all the workflows we use or just the workflow that it was validator.

[Brant Schroeder]

Just the scheme, trying to see what workflows are associated with what issue types.

[Aaron Andrade]

This the workflow scheme and the highlighted the HR Authorization workflow is where the validator was located.

[Brant Schroeder]

Can you share which transition(s) on the workflow it was located? Screenshot

[Aaron Andrade]

[Brant Schroeder]

Can you share the diagram view and highlight the transition that has the validation on it.

[Aaron Andrade]

[Brant Schroeder]

@Aaron Andrade hmmm I was hoping there might be a little more to it than that.  That is very simple and you really know your stuff.  Have you tried making a change elsewhere on the workflow and republishing to see if that resolves the issue?

[Aaron Andrade]

We have added other validators, but we can't test them to see if they work because this other validator keeps throwing the error. they show up on the right screen. I have tried everything I can think of. It's time I think to put in a support ticket with Atlassian.

[Brant Schroeder]

If you put the field back in place can you get rid of the validation error?   If you have other validators in place could it be that the error message possibly was duplicated in the validator and just needs to be updated?

[Aaron Andrade]

@Brant Schroeder That's what we had to do for the time being because HR couldn't approve any tickets for add/change/release employees. So we added the field back and made it to where they can check it. The funny part is we didn't add the validator back and it still works.

[Alex Koxaras _Relational_]

@Aaron Andrade can you do me a favor?

Export this specific workflow as XML, and open that file in the notepad. Then search for the string "please select". See if you get any result.

[Alex Koxaras _Relational_]

And you can also use this free app https://marketplace.atlassian.com/apps/1221996/smart-project-config-and-documentation?hosting=server&tab=overview, to export your project in a doc and search for this validator. If it nowhere to be found within your project, then something else is going on.

[Aaron Andrade]

Will do!

[Aaron Andrade]

@Alex Koxaras _Relational_ Here is what I found: Local Desktop Backup"

Never mind this is part of the new validator, there was no Please select

[Alex Koxaras _Relational_]

@Aaron Andrade did you find what was causing it?

[Aaron Andrade]

Not yet I have a ticket in with Atlassian to see if they can figure out what is going on. The last thing I want to do is make a whole new project, because one its a huge project and two we can't afford to have it down for a lengthy period of time.

[Alex Koxaras _Relational_]

Once you find out, kindly update this thread. Cheers!

[Aaron Andrade]

Yes the thread will be updated after Atlassian and I get to the bottom of it.

[Aaron Andrade]

@Alex Koxaras _Relational_ So there was an update issue. It was showing that it updated the workflow on the project, but the actual workflow wasn't updating at all. After several attempts it finally updated and fixed the issue.

[Alex Koxaras _Relational_]

So it was indeed a problem of the platform and the publish button wasn't working (sort to say)?

[Aaron Andrade]

Yes, and thankfully it was something small and seems to be working good now.

[Alex Koxaras _Relational_]

Hi @Aaron Andrade

Check if you have published the workflow changes (deletion of the validator). Check also the field confguration. You might have set this field as Required. If so, just make it optional.

[Aaron Andrade]

We did check the configuration after we kept getting the error and it was already optional.

[Dave Menconi]

There isn't enough information here for me to say for sure but...

This error appears to be a system that has a validator in place but has had the field being validated removed from the screen.

You say that you removed the validator. I'm fairly sure that there is still a validator in there.

Sometimes when I fix a workflow I forget to click on Publish. And workflows can be complicated so maybe there are several validators and there are still some left? Or maybe you didn't click "save" that last time on the change?

I can't say for certain but it sure LOOKS like there is still a validator in there somewhere...

DM
-- Jira often requires you to save twice; so remember to look for that second click that seals the deal!