The plugin should be able to parse commit message and create IssueDefined links

[e-backmark-ericsson]

Description

The SCC event has support to provide links to EiffelIssueDefinedEvents. There is currently no way to get such links into the SCC events sent from this plugin.

Motivation

To increase the trace-ability in source changes notified by this plugin to also include links to issues handled in the source change.

Exemplification

The commit message could contain a tag specifying what issue has been solved or partly solved with that source change. As the SCC event can contain RESOLVED_ISSUE or PARTLY_RESOLVED_ISSUE links to ID events it should be handled by this plugin. Whether the plugin should also send that ID event itself, or just lookup and link to existing ID events needs to be figured out.

Benefits

More complete trace-ability of issues handled in a source change

Possible Drawbacks

If the plugin itself would send the ID events it could be seen as a bit weird.

[e-pettersson-ericsson]

I think, from the perspective of this plugin it will be easiest (and perhaps most reasonable solution) to only look up existing IssueDefined events provided. This plugin is a Gerrit plugin, and I think sending IssueDefined events is outside of the intended scope of the plugin, since issues can be defined in other platforms. This of course, adds the dependency to some sort of event storage (Event repository perhaps?) but should it be critical? I.e. if the plugin fails to find the existing IssueDefined event from the provided event id, should the link not be included in the SCC event?

I noticed that a SourceChangeCreated event can contain 3 different link types to an IssueDefined event: 1) RESOLVED_ISSUE, 2) PARTIALLY_RESOLVED_ISSUE and 3) DERESOLVED_ISSUE. If the plugin should support, then it might support all of them, from my perspective. But how it will link from the SCC to the ID needs to be standardized somehow. I think the commit message, like you suggested, could be the only solution for commit author to provide this information to the plugin.

The commit message would need to contain a standardized syntax for how to provide such an event id to the plugin, and this needs to be thoroughly considered.