[
https://issues.jenkins-ci.org/browse/JENKINS-11839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161602#comment-161602
]
Jens H commented on JENKINS-11839:
----------------------------------
All projekts are connected to the mantis installation. The
"Trigger"-Commit-Message is only in the upstream project.
> Do not update mantis entry for all downstream jobs
> --------------------------------------------------
>
> Key: JENKINS-11839
> URL: https://issues.jenkins-ci.org/browse/JENKINS-11839
> Project: Jenkins
> Issue Type: Bug
> Components: mantis
> Affects Versions: current
> Environment: Jenkins 1.440
> Mantis-Plugin 0.20
> Mantis: 1.2.8
> Reporter: Jens H
> Assignee: sogabe
>
> I do have a set of jobs depending on each other.
> If I have a Mantis-ID in a commit message in "Project A" the Mantis issue is
> updated correctly from this project. But all other projects depending on
> "Project A" will also update this Mantis issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
