[
https://issues.apache.org/jira/browse/GEODE-58?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14588577#comment-14588577
]
Dan Smith commented on GEODE-58:
--------------------------------
To me the main value of auto-commenting on a ticket is to a) make sure we track
the commit hash that fixed the ticket, b) update the ticket with the
description of changes that fixed the ticket. And yeah, it would be really nice
if we could close the ticket with a commit too.
We haven't really set a policy on rebasing feature branches, but if people do
rebase a feature branch we may end up with messages that point to commits that
no longer exist. Maybe that's not a big deal? If people see value in seeing
updates to tickets for changes happening on feature branches, I can always
filter my mail :)
> git-JIRA integration is commenting when commits happen to feature branches
> --------------------------------------------------------------------------
>
> Key: GEODE-58
> URL: https://issues.apache.org/jira/browse/GEODE-58
> Project: Geode
> Issue Type: Bug
> Reporter: Dan Smith
> Assignee: William Markito Oliveira
>
> It looks like the git-JIRA integration is adding comments to tickets when
> commits are made to feature branches. See for example
> https://issues.apache.org/jira/browse/GEODE-38?focusedCommentId=14588468&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14588468
> I don't think that is the desired behaviour. We only want to a comment when a
> commit makes it develop.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
