Our standard of practice is to document the “why” in Jira. Then reference that card in the commit message.
This gives product owners the ability to embellish as they wish and reduces the need of the dev to repeat themselves.
This gives product owners the ability to embellish as they wish and reduces the need of the dev to repeat themselves.
But, perhaps the IDE could retrieve the details of the jira card, and help pre-generate the commit message from it.
If only tickets would be part of the repository itself from the beginning, that would be much simpler IMO.
Giving agent scoped access to ticket system. Whis is this obvious answer not the obvious solution?