Conversations over the years have shown me that DDD was a great inverse marketing tool, ironically pushing developers towards the embedded debugger UI in their favorite IDEs... despite DDD itself being indeed very powerful. But even "usefulness over aesthetics" has its limits!
I've found it a very powerful yet compact way to visualize the state of a program when debugging.
Compare the Linux commit history, every commit has its full context and explanation and they do not rely on external systems.
I"m working on a repository that uses at least four different jira ticket number formats. All commits should have a jira reference but I think only the current format can still be looked up. And maybe the predecessor if you know what jira field to query. All the rest are lost in corporate limbo. Not that those tickets added much more context to the actual commit...
So yeah, always write your commit messages as standalone as possible.