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

Issue is updated with reports that contains other unrelated issues

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      It reports in the right task, but it would tag a whole bunch of unrelated tasks too though.

      Jira Issue Updater Plugin

        Attachments

          Activity

          Hide
          warden Radek Antoniuk added a comment -

          Seems that should be jenkins-jira-issue-updater issue.

          Show
          warden Radek Antoniuk added a comment - Seems that should be jenkins-jira-issue-updater issue.
          Hide
          laszlomiklosik Laszlo Miklosik added a comment -

          Hi,

          can you provide more details?

          Not sure what you mean by:

          Issue is updated with reports that contains other unrelated issue

          How can an issue be updated with reports?

          A concrete example explained or the reproduction path is needed in order to fix this issue.

          Thanks!

          Show
          laszlomiklosik Laszlo Miklosik added a comment - Hi, can you provide more details? Not sure what you mean by: Issue is updated with reports that contains other unrelated issue How can an issue be updated with reports? A concrete example explained or the reproduction path is needed in order to fix this issue. Thanks!
          Hide
          isparkes Ian Sparkes added a comment -

          Sounds to me like the search term was too loose. The plug in is designed to be able to update more than one issue each update. Narrowing or widening the scope of the update is surely up to the configurer isn't it?

          Show
          isparkes Ian Sparkes added a comment - Sounds to me like the search term was too loose. The plug in is designed to be able to update more than one issue each update. Narrowing or widening the scope of the update is surely up to the configurer isn't it?
          Hide
          chrisaaaaa Chris Amis added a comment -

          +1 this issue, I hit the same issue.

          I have 1 change which is updated as expected, then it seems to read dependency changes and update all those issues too.

          Seems to be by design;

          "Selects all issues found in change lists or parameters of current build or in any of changed dependencies. Selection is using globally configured pattern that is evaluated against commit message"

          But how do I edit this globally configured pattern to take out the dependency stuff?

           

          All current versions (bleading edge and LTS jenkins)...

          Show
          chrisaaaaa Chris Amis added a comment - +1 this issue, I hit the same issue. I have 1 change which is updated as expected, then it seems to read dependency changes and update all those issues too. Seems to be by design; "Selects all issues found in change lists or parameters of current build or in any of changed dependencies. Selection is using globally configured pattern that is evaluated against commit message" But how do I edit this globally configured pattern to take out the dependency stuff?   All current versions (bleading edge and LTS jenkins)...
          Hide
          chrisaaaaa Chris Amis added a comment -

          An example, which results in multiple updated tickets (comments added).

          The expected update is just to WSGSWPROC-16. The extra updates are all the changes implicated in builds #876..#880.

          If I grab the build info via the json api I just get the single change in the changeset.

          I have forked the code but cannot work out where it gets this list of dependencies, sorry I write low level embedded C, so this stuff is way out of my area.

          I tried other techniques like custom jql or the explicit option, but I am stymied because it does not translate $JIRA_ISSUES to the relevant JIRA key (Jenkins logs show JQL lookup failing because of the $ character).

          Please help, I am being inundated under hundreds of pointless updates and all the associated emails.

          Chris

          ####

          Revision: 15604
          Changes

          1. WSGSWPROC-16 - Add ability to make normal build just do a package, just put nobuild.flg in checkout root. (detail)
            by Chris Amis

          Changes in dependency

          1. W5400_trunk  #876-r15598-2017-10-13 14:59 →  #880-r15603-2017-10-17 09:08 (detail)

           

           

           

          Show
          chrisaaaaa Chris Amis added a comment - An example, which results in multiple updated tickets (comments added). The expected update is just to WSGSWPROC-16. The extra updates are all the changes implicated in builds #876..#880. If I grab the build info via the json api I just get the single change in the changeset. I have forked the code but cannot work out where it gets this list of dependencies, sorry I write low level embedded C, so this stuff is way out of my area. I tried other techniques like custom jql or the explicit option, but I am stymied because it does not translate $JIRA_ISSUES to the relevant JIRA key (Jenkins logs show JQL lookup failing because of the $ character). Please help, I am being inundated under hundreds of pointless updates and all the associated emails. Chris #### Revision: 15604 Changes WSGSWPROC-16  - Add ability to make normal build just do a package, just put nobuild.flg in checkout root. ( detail ) by  Chris Amis Changes in dependency W5400_trunk   #876-r15598-2017-10-13 14:59  →  #880-r15603-2017-10-17 09:08  ( detail )      

            People

            Assignee:
            isparkes Ian Sparkes
            Reporter:
            travis_ly Travis Ly
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Dates

              Created:
              Updated: