I have tried different approaches, but on my latest project, we used the following:
Have on the Stories a field labeled "Solution" to record what the developer did and where she/he did it.
After finishing the development the person would write down her/his report without forgetting to state the full path(s) to the change(s) (eSpace > Screen/Action > ScreenAction > ...)
When the report was complete, the story would move to "Waiting for review" and another developer would pick up the "Do review" sub-task and move the story to "In Review".
If "issues" were found, the reviewer would create sub-tasks on the story and assigned those to the developer. Again, it was necessary to state where the "issue(s)" was/were found and, maybe, put some screenshots. If needed, the developer and the reviewer would do a meeting to clarify things and share ideas.
The advantages of this approach were:
- There is always, at least, two team members knowing why and how something was done.
- There is more sharing of Outsystems knowledge between team members.
- We could search in Jira for all stories that changed a screen/action.
It's important to state that having the solution in Jira wouldn't mean the code wouldn't have comments; in fact, part of the reviewer's task was to be sure the more complicated logic had the necessary comments.
I hope this helps!
Regards,
Ricardo