post-function to "set or create a project property" does not work

Issue #429 resolved
noname created an issue

I’m evaluating the jira workflow toolbox plugin for my company. I’m running Jira 7.0.9 and bitbucket 4.9.1 on a 2-node cluster.

I have a hidden transition between 2 steps (a -> b) activated by a trigger - when a pull request is created.

I have a post-function rule to create/set a project property to 1. “Project property in failure_count will written with the value stored in 1. If property doesn't exists the property will be created in project description.”

I also have a 2nd hidden transition (b -> a) to create/set the project property to 0 when the pull request is declined or merged.

In both cases the project property is not getting changed reliably even though the transitions work perfectly fine all the time.

It will work fine a few times, then stop updating. I can see that the property in the project description has not changed.

I’ve tried moving the post-function order from the beginning to the end which didn’t work.

I’ve tried putting the post-function in twice both at the beginning and the end order, which also didn’t work.

I was previously testing 2.2.14 and upgraded to 2.2.21 still with the same behavior. It works a few times but then stops updating. It's sporadic.

Thanks.

Comments (7)

  1. Fidel Castro Armario repo owner

    Hi,

    Thanks for reporting the problem. I will try to reproduce it. Is it possible that you send me your server's log file? I would like to exam it in detail looking for error messages related with the problem. You can send it to support@workflowarts.com.

    Fidel

  2. noname reporter

    I emailed the server logs to you.

    However I found another issue while testing.

    As mentioned before we're using Datacenter versions of Jira + Bitbucket with a 2-server configuration. While testing we were also able to produce a scenario where the project property did update, but the change was not visible to everyone viewing the property in the project admin screen. One person saw the new value, and the other person saw the old value.

    So could there also be a syncing problem (between nodes)? Can the plugin handle a multi-server configuration?

  3. Fidel Castro Armario repo owner

    Thanks for the additional information. Please, give me some time to try to replicate your configuration, and to reproduce your problem.

    The plugin is Data Center compatible, and this is the first issue received in relation to it. Syncing project configuration, like project description, is responsibility of the cluster.

    Please, run JIRA Data Center Health Check Tools. You might have a problem with cluster cache replication. This would explain the behavior you are experiencing.

  4. noname reporter

    We ran the health-check and it came back clean.

    We were able to find a work-around so we don't need the project property any longer. You can close this issue.

    Thanks for all the help and the quick response.

  5. Log in to comment