The difference between smart commits and workflow triggers?

[Deleted user]

What is the difference between smart commits (mentioned here)

https://confluence.atlassian.com/adminjiracloud/enable-smart-commits-776830276.html

And workflow triggers (mentioned here)?

https://confluence.atlassian.com/adminjiraserver075/configuring-workflow-triggers-935391509.html

It seems like smart commits do more, in that you can comment as well as transition a ticket with a bitbucket commit (which is the real feature & functionality I want).

Even though they seem to accomplish very similar things the instructions don't mention each other so I'm confused if I need both.

[Earl McCutcheon · Accepted solution]

Hi Dan,

The difference is manual customizations vs automated action.

A Workflow Trigger is listening for the commit then completing the workflow action defined, where smart commits are additional commands to trigger specific actions added into the commit itself.

Workflow Triggers automate the follow up action when a commit is done, useful when you want the same action applied with every commit

Smart commits allow for custom manual actions in the commit, useful for follow up actions when different action is needed for each commit, i.e. sometimes a transition is needed, and sometimes only a comment is needed.

Regards,
Earl

[Deleted user]

Many Thanks Earl! That's great. Smart commits is what we are after then.