Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-44691

JiraTestResultReporter-plugin:Correlates a new test failure with a resolved jira issue

      We have a case where a particular test failed, passed and consequently failed again. The JIRA result reporter plug in as you would expect opened an issue the first time the test failed, then when it went away it resolved the issue but when it reappeared instead of reopening the bug or opening a new issue for the same test, it simply related it to the existing bug which is in the state of resolved, and indicated in the Junit report the issue was "resolved".

      It seems like the plugin is not taking into account that the resolution of this bug happened prior to the new failure.

      Is there a way around this? are you guys working on any kind of options for having the plug in reopen a previously resolved issue?

          [JENKINS-44691] JiraTestResultReporter-plugin:Correlates a new test failure with a resolved jira issue

          Catalin Luta added a comment -

          lbilbao, could you please tell us what version of the plugin you are using?

          We're currently not looking at the state of the issue. We've had some problems in our working environment in which we've had random test fails due to flakiness. We've decided on the current model based on this: The plugin will keep the previous link until the user deems that the current issue is different from the last one and unlinks the issue by hand. 

          We're planning a release in June, though, and we can take a look at adding an option of ignoring linkages when a certain state is present. We'll keep you up to date with this

          Catalin Luta added a comment - lbilbao , could you please tell us what version of the plugin you are using? We're currently not looking at the state of the issue. We've had some problems in our working environment in which we've had random test fails due to flakiness. We've decided on the current model based on this: The plugin will keep the previous link until the user deems that the current issue is different from the last one and unlinks the issue by hand.  We're planning a release in June, though, and we can take a look at adding an option of ignoring linkages when a certain state is present. We'll keep you up to date with this

          Code changed in jenkins
          User: Andrei Tuicu
          Path:
          src/main/java/org/jenkinsci/plugins/JiraTestResultReporter/JiraTestDataPublisher.java
          src/main/java/org/jenkinsci/plugins/JiraTestResultReporter/JobConfigMapping.java
          src/main/resources/org/jenkinsci/plugins/JiraTestResultReporter/JiraTestDataPublisher/config.jelly
          http://jenkins-ci.org/commit/JiraTestResultReporter-plugin/7321c99c2d6cb415002dde12b14e332ea7c61352
          Log:
          JENKINS-44691 - Correlates a new test failure with a resolved jira issue

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Andrei Tuicu Path: src/main/java/org/jenkinsci/plugins/JiraTestResultReporter/JiraTestDataPublisher.java src/main/java/org/jenkinsci/plugins/JiraTestResultReporter/JobConfigMapping.java src/main/resources/org/jenkinsci/plugins/JiraTestResultReporter/JiraTestDataPublisher/config.jelly http://jenkins-ci.org/commit/JiraTestResultReporter-plugin/7321c99c2d6cb415002dde12b14e332ea7c61352 Log: JENKINS-44691 - Correlates a new test failure with a resolved jira issue

          Christian added a comment - - edited

          lbilbao The new option autoUnlinkIssue was added (available since https://github.com/jenkinsci/JiraTestResultReporter-plugin/releases/tag/JiraTestResultReporter-2.0.15 ). Did that solve the problem for you?

          Christian added a comment - - edited lbilbao The new option autoUnlinkIssue was added (available since https://github.com/jenkinsci/JiraTestResultReporter-plugin/releases/tag/JiraTestResultReporter-2.0.15 ). Did that solve the problem for you?

            catalinluta Catalin Luta
            lbilbao Lourdes Bilbao
            Votes:
            1 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: