Error with validator

Issue #71 resolved
Former user created an issue

When executing a transition, we get the following error: An unknown exception occured executing Validator com.fca.jira.plugins.workflowToolbox.UserInFieldRolValidator@a20e1a root cause: ProjectRole can not be null

See images

Comments (5)

  1. Martin Aparicio

    I'm the submitter. We are using JIRA 5.2.11 standalone on Solaris. Let me know if you need more info. As you can see from the screen shots, we are unable to advance in our workflow. I don't see a way to edit the validator. I do have backend access to the DB. If this is not a quick fix, I can just recreate the transition. Please advise.

  2. Fidel Castro Armario repo owner

    Hi Martin,

    I will need the server's log file to see exactly which line of code is causing the problem. I will need only the part related with the exception.

    It's a very strange problem, since this feature is very old in the plugin (hasn't changed since version 2.0.25, released on 3rd May 2013), and no other problem has been notified since then. I have noticed that your transition configuration dates from an earlier version, since a parameter introduced in version 2.0.25 is not present. Anyway, that shouldn't be a problem, and I have reproduced a migration from version 2.0.24 to 2.1.19 in JIRA 5.2.11 without any problem.

    Can you please, give me some information about the circumstances where the problem has arisen? Have you updated the plugin recently?

    Can you try updating to version 2.1.20 of JIRA Workflow Toolbox?

    Thanks

  3. Martin Aparicio

    The validator shown in the ALL view is actually mislabeled. I went ahead and deleted it, and the UserInRole validator was removed. Sorry, I didn't capture the logs. It was a prod problem. Thanks.

  4. Fidel Castro Armario repo owner

    Hi Martin,

    Then, did you solve the problem? Can I close the issue?

    Regards,

    Fidel

  5. Fidel Castro Armario repo owner

    I close the issue, since it seems to be solved. Please, reopen the issue in case you keep having problems.

  6. Log in to comment