Most sync customers remove transition rules for the technical MF Connect user account(s), only.

I.e.: Nothing changes for normal Jira users - but MF Connect is able to transition to any state. Same in Octane...

We might be able to implement simple "awareness" of transition rules in MF Connect - that would however not work sufficiently well enough as many customers have quite complex transition and validity rules that we would not be able to analyze and "apply" automatically.

As a rule, MF Connect does NOT sync each and every version change - it only syncs last most current state. There are many reasons for this behavior and this is unlikely to change in the near to medium term (or even ever)...

I have been testing this out - Octane appears to work even without any phase transitions in place - is this because the API user is getting special treatment in Octane? It can go from Open to Closed ok even though no pathway exists in the workflow.

Jira looks like it is currently blocked from going to a status that is not linked to the current one, so all rules will need to be removed for our Jira user.

Yes - most Octane API calls seem to bypass the workflow rules.

However, as this is not a well-documented behavior, it might change in the future.

For Jira, special accommodations for the MF Connect account(s) are strongly recommended (dedicated boards, dedicated "Create" screens, dedicated workflow rules).

Possible workaround:

Create a specific role  in Jira able to switch issues into every status and give this role to the user used by Connect.

Only this role should be able to see those shortcuts.

Of course it's a bit cumbersome.

Hi,

Do you have some info about what could change?

Actually, I would be happy to provide MF Connect the rights to jump from one status to another,  in both side Jira and Octane, without taking into account the transitions.

As it usually happens that users forget to update their status and need to change the status 2 times,  in less than 1minute in order to be up to date.

We are planning to use the workaround mentionned below by Marco.

Thanks

Guillaume

It looks like current version of Octane on SaaS has locked this down - found our API user cannot now move between test phases that aren't part of workflow.

Looks like I will have to create transition rule between every phase and lock down the API user to a specific user group, then apply condition to each transition rule. Unless anyone has alternative ideas?

Octane looks to have blocked this now. Bit of a pain to add all transition rules in to Octane now. Sigh.....

Please create an MF Connect support case (via Octane) for this.
This sounds more like an unintended API change than a planned one.
This doesn't help you immediately - but we need to look into this at more detail - see if it can be addressed maybe by additional access rights - or if we (the MF Connect team) need to work with the Octane team to fix/address this behavior.

Can you please check the following two parameters in your affected site/space configuration:

INCLUDE_PREDEFINED_SYNCHRONIZATION_CLIENT_TYPES
SYNCHRONIZATION_CLIENT_TYPES

Both should be set to "true".

Please note that this does not change the need to urgently create a support case for this!

These parameters do not exist on our SaaS instance. A ticket has been raised