-
Bug
-
Resolution: Unresolved
-
Minor
-
None
As I have reported previously by chat, we are experiencing some strange behaviour in JIRA plugin at times. We have somewhat recently started using jira plugin to allow jenkins users to select the relevant jira issue when running the jobs.
In the jenkins job, the parameter configuration is like !
!
and on the Post-build Actions we have a "Update relevant JIRA issues" action, as shown in !
!
In the JIRA ticket we can see the user fire the job #1803 (there is a typo in the copy paste, but I double checked that), and we have no message whatsoever of that job, but we do have a message from the job #1806:
!
!
[JENKINS-32560] jira-plugin generating message in the wrong ticket
| Description |
Original:
As I have reported previously by chat, we are experiencing some strange behaviour in JIRA plugin at times. We have somewhat recently started using jira plugin to allow jenkins users to select the relevant jira issue when running the jobs. In the jenkins job, the parameter configuration is like !!screenshot138.png!! and on the Post-build Actions we have a "Update relevant JIRA issues" action, as shown in !!screenshot139.png!! In the JIRA ticket we can see the user fire the job #1803 (there is a typo in the copy paste, but I double checked that), and we have no message whatsoever of that job, but we do have a message from the job #1806: !!screenshot140.png!! |
New:
As I have reported previously by chat, we are experiencing some strange behaviour in JIRA plugin at times. We have somewhat recently started using jira plugin to allow jenkins users to select the relevant jira issue when running the jobs. In the jenkins job, the parameter configuration is like !!snapshot138.png!! and on the Post-build Actions we have a "Update relevant JIRA issues" action, as shown in !!snapshot139.png!! In the JIRA ticket we can see the user fire the job #1803 (there is a typo in the copy paste, but I double checked that), and we have no message whatsoever of that job, but we do have a message from the job #1806: !!snapshot140.png!! |
As a matter of fact, the job 1806 message went to 4 tickets: one that appears to be the right one, and then other three had no messages whatsoever, but the job runs used in them had all failed.
David Brown
added a comment - This sounds like the same issue we are facing (using Jenkins version 1.598 and JIRA plugin version 1.38).
What I've noticed is that the incorrect updates have only the first line of comment, e.g.
"SUCCESS: Integrated in DEV-16-2 #455"
whereas a legitimate update will include the full changeset description on subsequent lines.
In my view this issue should have a higher Priority than Minor/Trivial as users are being misled into believing that changes have been included in builds when they have not been.
David Brown
added a comment - This sounds like the same issue we are facing (using Jenkins version 1.598 and JIRA plugin version 1.38).
What I've noticed is that the incorrect updates have only the first line of comment, e.g.
"SUCCESS: Integrated in DEV-16-2 #455"
whereas a legitimate update will include the full changeset description on subsequent lines.
In my view this issue should have a higher Priority than Minor/Trivial as users are being misled into believing that changes have been included in builds when they have not been. David Brown
added a comment - Hi alexeiz,
Just curious, what version of Jenkins and JIRA plugin are you seeing this issue in please?
As I said, I'm seeing the issue with JIRA plugin version 1.38 and I wonder if it is resolved in a later version.
David Brown
added a comment - Hi alexeiz ,
Just curious, what version of Jenkins and JIRA plugin are you seeing this issue in please?
As I said, I'm seeing the issue with JIRA plugin version 1.38 and I wonder if it is resolved in a later version. hi davidbrown92, we are currently running:
- Jenkins ver. 1.642
- JIRA plugin 2.1 (2.2 is out there, going to update soon)
David Brown
added a comment - Thank you for your update, alexeiz . David Brown
made changes -
| Attachment | New: screenshot-1.png [ 32078 ] |
David Brown
added a comment - We are seeing two different formats to the message. A valid message has multiple lines including the JIRA reference, commit comments and changeset details. Incorrect (misleading) messages contain a single line “SUCCESS: Integrated in PROJECT #BuildNum”.
The following image shows a good followed by a bad message as seen on a single JIRA ticket:
We are using Jenkins version 1.598, JIRA Version v6.3.15 and JIRA plugin version 1.38.
Can someone please confirm whether this is a known issue?
David Brown
added a comment - We are seeing two different formats to the message. A valid message has multiple lines including the JIRA reference, commit comments and changeset details. Incorrect (misleading) messages contain a single line “SUCCESS: Integrated in PROJECT #BuildNum”.
The following image shows a good followed by a bad message as seen on a single JIRA ticket:
We are using Jenkins version 1.598, JIRA Version v6.3.15 and JIRA plugin version 1.38.
Can someone please confirm whether this is a known issue?
I showed this ticket to the team and one of the guys commented this:
I have not run that test yet, but it might be a pointer to the problem.