We recently upgraded to JIRA structure V3.2.0 from V2.x
The question is that, it is not clear when to use Automation and when to use Synchronizers..
I cannot see a reason right now why we should still use Synchronizers? Can we start disabling synchronizers and switch to Automation generators? Is there still any specific use case for Synchronizers?
Eugene here from ALM Works. The short answer would be - we recommend using Automation whenever possible.
Automation was created as a new way to build dynamic structures and it's much more intuitive and safer too. It also offers better performance in most cases.
The key difference is that with Automation structures are "generated" when you open them, based on the rules that you define. With Synchronisers, there will be a process that continuously monitors changes in JIRA and Structure and makes necessary updates. If you define contradicting synchronizer rules, you can get some unwanted changes to your JIRA data - with Automation this risk is minimised practically to zero.
Plus functions like grouping and sorting allow you to build all kinds of issue views, which was not possible with synchronizers. For example, it's really easy to do capacity planning by grouping your issues first by sprint and then by assignee or team and see totals for the estimates and other fields rolled up to the sprint/user/team level.
If you are trying to build a certain structure and have some questions what's the best way to do it - please don't hesitate to contact us through our JIRA or email us at firstname.lastname@example.org.
I hope this helps,
Thanks for your answer! So, synchronizers can be replaced by Automation and Automation has additional features as well.. There is no specific use-case for creating synchronizers instead of automation in the structure boards any more. Can you confirm?
Thanks and regards,
Hi Fazila et al,
There is a use case to use a synchronizer rather than generators.
If you are using epic link and issue link relationships between issues, the link synchronizer can be configured with a sub-issue filter
"Epic link" is EMPTY to prevent that an issue is added (again) in the hierarchy when it already has been added by the agile synchronizer or the "epics and stories" generator. When using the "linked issues" generator, it would automatically be added twice at the same place when the epic link and issue link contain the same parent.
Of course, it is arguable that having both epic link and issue link (to the same parent issue) means the issue should appear twice in the hierarchy. However, with Structure v2 when having both Agile and Link synchronizers on a structure would automatically add (and even replace) the Epic or Issue link when (manually) adding one of these links, and vice versa. So coming from Structure v2 it is quite natural to have both Epic and Issue links to the same parent issue.
Switching to Structure v3, I don't want to count double on accumulated estimates, so somehow I need to prevent the issue to appear twice at the same place.
What Frank says is certainly true and there are actually other cases, when you cannot get something with automation, but you can do that with synchronizers. But we are working on improving the automation rules to make them more flexible - for example, filters for parents and children for the links extender is one of the top items in our backlog.
So to sum it up - when you create a new structure, we recommend to try automation first and if you cannot get it working - please contact us and we'll see if there are some workarounds for your specific use case. If it's not possible, but possible to do with the synchronizers - we'll suggest the best option.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
This September 6-7, hundreds of Atlassian App developers will flock to Barcelona Spain to build skills, discover product roadmaps, meet face-to-face with the Atlassian team, and learn how to extend t...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG