My idea was that this represented a list of issues that the ARM addresses. But it is naturally also of value to track the issue(s) that are the result of the arm.  Have two lists of issues? 

Alternatively, have one redmine issue that tracks the arm; it is created (at the latest) when the arm reaches Submitted state. But it could also be created earlier as this gives the ability to link the ARM issue to other redmine issues (i.e with the intent that "This ARM will fix/supersede these issues". If we have a redmine issue, then the metadata.json only needs this one issue.