Details
-
Suggestion
-
Resolution: Fixed
-
P2: Important
-
None
-
None
-
None
-
d8a697730 (master), ee15f89fd (dev), 6a343fd31 (dev), 44a2c39aa (6.8), 0ee367f19 (6.7), e6429f674 (tqtc/lts-6.5), bf8ce130a (tqtc/lts-6.2)
Description
A new keyword, "Reopens:", is proposed for commit message footers which will trigger the reopening of a Jira issue.
Proposed behavior is twofold:
- When the Reopens footer appears in conjunction with the Fixes footer, it will reopen the specified issue upon pushing the first patchset to Gerrit. (F.ex. A follow-up change to fix an issue by which the first patch that closed the change did not completely resolve the bug)
- When the Reopens footer appears without the presence of Fixes, it will reopen the specified issue upon merging the change. (F.ex. A revert that once merged makes the tagged Jira issue outstanding once more)
Jira issues implicated by Reopens should be tagged with the relevant commit once merged.
Further, changes which include a revert in the commit message should tag the relevant Jira issue with the merged sha, even if the Reopens keyword or any other keyword is not present on the change. This relation can usually be identified by examining the original commit the revert relates to.