multiple JIRA:xxxxx lines in commit messages?


Sam Hague <shague@...>
 

Thanh,

thanks for the comment about not having a space between the JIRA: xxxxx and the Change-Id - all metadata should be continuous and together in the footer.

Thanh got me thinking if it is OK to have multiple JIRA:xxxx lines in a message and if it would link them correctly in jira. We have blueprint feature specs and then bug fixes on those features. It helps if we could list both jiras so that we can track all changes for a feature. Do you see any problems with this?

Thanks, Sam


Andrew Grimberg
 

On 10/23/2018 07:48 AM, Sam Hague wrote:
Thanh,

thanks for the comment about not having a space between the JIRA: xxxxx
and the Change-Id - all metadata should be continuous and together in
the footer.

Thanh got me thinking if it is OK to have multiple JIRA:xxxx lines in a
message and if it would link them correctly in jira. We have blueprint
feature specs and then bug fixes on those features. It helps if we could
list both jiras so that we can track all changes for a feature. Do you
see any problems with this?
Multiple issue indicators is just fine. I do this all the time with the
LF Gerrit for changes I'm rolling out that affect multiple different issues.

Your commit message just ends up looking like:

--[cut]--
$SUBJECT

$BODY

JIRA: XXXXX-NNNNN
JIRA: YYYYY-ZZZZZ
Change-Id: $CHANGEID
Signed-off-by: $DCO
--[/cut]--

-Andy-

--
Andrew J Grimberg
Manager Release Engineering
The Linux Foundation