You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@yetus.apache.org by "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2019/01/11 19:05:00 UTC

[jira] [Updated] (YETUS-742) rework external communications

     [ https://issues.apache.org/jira/browse/YETUS-742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Allen Wittenauer updated YETUS-742:
-----------------------------------
    Summary: rework external communications  (was: github/jira bridge traffic control)

> rework external communications
> ------------------------------
>
>                 Key: YETUS-742
>                 URL: https://issues.apache.org/jira/browse/YETUS-742
>             Project: Yetus
>          Issue Type: Improvement
>          Components: Test Patch
>            Reporter: Allen Wittenauer
>            Priority: Major
>             Fix For: 0.10.0
>
>
> A pull request that references a JIRA doesn't update the JIRA.  I believe this is because we have coded in the belief that JIRA is the starting reference point.  This should be tunable such that if test-patch starts as the PR as the starting point, it should definitely be updating JIRA.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)