For Jira 7.13 version same error.

Hi,

It's been almost 2 years since the last update of this bug and I believe this bug priority must be a BLOCKER. Here's why:

1. We are enforcing code work and code review and no JIRA ticket with code changes must continue for closing when the related code review is closed for that change.
2. What I am reading from the support team and from this ticket is that Fisheye/Crucible workflow conditions are skipped when JIRA users with Fisheye account are not logged in Fisheye. What about those JIRA users who don't have Fisheye account? Are code enforcement not valid for them? Or they are able to break such enforcement regardless of the transition conditions explicitly mentioned.
3. My current Application Link Type is OAuth with impersonation

Please, fix this as soon as possible. Otherwise,non-Fisheye JIRA users will discover this hole and exploit it and me as an Atlassian Admin, won't be able to mitigate.

Hi pboev291022425,

Thanks for showing your interest in this fix. 
Unfortunately, this is currently not in our short-term backlog as we are currently working through higher priority issues in other areas of JIRA.

Having said that it is still an issue we would like to address in the long term, as it gathers more votes and interest from other customers. Could you please add your vote to this?

Please also do watch the issue, I will update it as soon as more information is available on it.

Ignat,
JIRA Bugmaster.

When can we expect this to be fixed?
Or is there some workaround?
We have teams with strict business processes, where certain transitions (for example resolving issues) must not be available if there are open code reviews.
With this condition being bypassed for some users (that are not authenticated) we may end up with resolved issue, that still has open code reviews.
We are being audited regularly for our quality management processes and if auditors find that we are resolving issues with open code reviews (while our process documentation states that this must not happen) they will conclude that we are not properly monitoring the application of our own processes.

We try to incorporate such business process conditions into our workflows, to minimize the chance for human errors and build the process into the system.
But with such "random" bypassing of workflow conditions we won't comply to our own processes.

Also happens in 7.0.2

Cloned as https://jira.atlassian.com/browse/FE-5727

Thanks for the clarification, ohernandez@atlassian.com.

Hey malmeida,

From another case, we found out all these conditions are in the Fisheye Plugin, so this needs be looked at by the FishEye team.

Cheers,
Os.

Hey ohernandez@atlassian.com,

These are all provided by JIRA.

Hi malmeida,

Is this condition provided by JIRA or a third party plugin?

Cheers,
Os.