On 05/07/2018 01:53 AM, Robert Varga wrote: > On 04/05/18 23:25, Andrew Grimberg wrote: >> On 05/04/2018 12:47 PM, Robert Varga wrote: >>> On 04/05/18 17:07, Andrew Grimberg wrote: >>>>> Hi Robert, >>>>> >>>>> Jira hides them by default. If you click the tiny down arrow the top >>>>> right of the Gerrit Reviews table, it will open a small menu. From this >>>>> menu click "Show All Reviews". Then it will show all the merged ones. >>>>> >>>>> I think it caches that setting per session though as I've had to click >>>>> on this a few times. I'm not aware of a way to make the setting permanent. >>>> No, there's no way to do so. It's an extremely common question we see :-/ >>> >>> Oh crap, but that effectively means we need to explicitly link them in >>> comments if we want to find them in future :( >> >> Yes, that's correct. > > Alright, but then ... > >>> Do I understand it correctly that this is something the Gerrit >>> integration plugin cannot do and would be feasible via, for example, >>> https://marketplace.atlassian.com/plugins/com.xiplink.jira.git.jira_git_plugin/cloud/overview >>> ? >>> >>> I am not suggesting we buy it, it's just so I understand where the >>> problem is. >> >> My understanding of that plugin is that it too would require that you >> have information in the commit message that would link it to the >> appropriate JIRA issues. >> >> There's no way around that if you want to have JIRA automatically find >> changes related to a particular issue. >> >> So, just as you need to state the issue in the commit message for Gerrit >> to link to the JIRA, JIRA needs that _same_ information to be able to >> find changes related to a particular issue. > > ... could we perhaps hook an action when a Gerrit patch is merged to > post a comment to the JIRA issue? > > That way the plugin tracks open issues and we do not have to manually > link issues to not lose track of merged issues... > > Regards, > Robert
The JIRA integration for Gerrit will list _all_ changes that have a <PROJECT>-<ISSUEID> in the change comment. They may, or may not, be visible to you when you hit an issue. The integration doesn't always pull things up. Forcing it to refresh / show all will do that. For instance at the time of this email [0] has multiple changes open, and multiple changes already closed. [0] https://jira.opendaylight.org/browse/DOCS-69?gerritReviewStatus=All#gerrit-reviews-left-panel There's no need for a comment to be added to JIRA, it's going be able to find all the issues that have been comment tagged to it. -Andy- -- Andrew J Grimberg Lead, IT Release Engineering The Linux Foundation
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Discuss mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/discuss
