Considerations for JIRA Workflow Users

It is possible to set values for an issue in AccuWork that conflict with your JIRA workflow rules. For example, in AccuWork, you might be able to change an issue’s Status field value from Open to Reviewed. If your JIRA workflow rules specify that an issue’s status can change from Open to only In Progress, Resolved, or Closed, however, the synchronization for that issue will fail because the issue’s status violates the JIRA workflow rule.

You can work around potential JIRA workflow rule conflicts in one of these ways:

Use one-way synchronization for specific fields

. By default, AccuSync performs two-way synchronization for all issue data. Changes made to an issue in AccuWork are written to the JIRA issue each time synchronization is performed, and vice versa. You can override the synchronization type on a field-by-field basis if you choose. For example, you might decide that you do not want changes made to an issue’s Status field in AccuWork to be written to the JIRA record during synchronization. In this case, you could set the synchronization type for the Status field to one-way, specifying JIRA as the master server. Once you do this, changes made to the issue’s Status field in JIRA will be written to AccuWork when the issues are synchronized, but not vice versa. AccuRev recommends using per-field one-way synchronization to avoid JIRA workflow rule conflicts.

Tip: If you use one-way synchronization for fields related to your JIRA workflow (like Status, for example), consider defining that field as read-only in the AccuWork schema. This will prevent users from manually changing the value of the field in AccuWork and ensure that the field always displays the correct and current value.

Emulate AccuBridge behavior in AccuSync

As mentioned previously AccuSync is fully bidirectional; its predecessor, AccuBridge, performs one-way synchronizations, writing JIRA issue data to AccuWork, but not vice versa. If you want, you can configure AccuSync to emulate AccuBridge functionality by changing the default synchronization type from two-way to one-way for all of the synchronization patterns defined for your AccuSync configurations.

Replicate your workflow logic in AccuWork

Finally, you can use AccuWork schema validation to allow only certain values for a given field or setting certain fields required to enforce JIRA workflow restrictions in AccuWork. This approach, however, can be more time-consuming to implement than the other two, and you should consider whether one of the other approaches might provide the functionality you require.