)]}'
{"releasenotes/notes/changing-context-in-delayed-calls-78d8e9a622fe3fe9.yaml":[{"author":{"_account_id":6732,"name":"Lingxian Kong","email":"anlin.kong@gmail.com","username":"kong"},"change_message_id":"34394d4e8f0a15603a35e0fad08f9d69dcd2854c","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":4,"id":"5a710552_c3a6c352","line":10,"updated":"2015-12-16 14:13:13.000000000","message":"Just a suggestion, I would write something like the following:\n\nsecurity:\n  - Fixing `bug 1521802 \u003chttps://bugs.launchpad.net/mistral/+bug/1521802\u003e`_ that sub-workflow execution was run/saved under the wrong tenant in cron trigger periodic task in multi-tenancy deployment.","commit_id":"c58b428d047d2a59b9014bcdb17d9067f7b1269a"}]}
