xl8bot
1
Originally asked by SANDEEP ADE on 04 October 2019 (original question)
Hi ,
we have some of the jira statuses which move to the next status automatically
ex:If a defect status is marked as “Approved” it transitions into “IT OPS to Deploy” automatically
so these kind of auto transitions are not getting updated in ALM ,because there is no event triggered when the status transtion happens automatically.
In such cases there is a descrepancy in the status ,and sometimes the status is getting set to the old status whichever is there is ALM.
How to over come this issue?
see attachment for example.
xl8bot
2
Answer by SANDEEP ADE on 05 November 2019
below are the lines from alm end
defect.summary = replica.summary
//defect.description = replica.description
defect.attachments += replica.addedAttachments
defect.attachments -= replica.removedAttachments
defect.commentsArea = commentHelper.mergeCommentsIntoCommentsArea(defect, replica)
defect.status = qcHelper.getStatus(replica.status?.name)
and below are the lines from Jira
StatusSync.receiveStatus(
true,
[
“Open”: “Requested”,
“Approved” : “Approved”,
],
replica,
issue,
nodeHelper
)
xl8bot
3
Answer by André Leroy-Beaulieu Castro on 04 October 2019
Hi Sandeep,
Can you show us the lines that you’re using in your scripts to synchronize status with HP?
This documentation link should serve as a guide https://docs.idalko.com/exalate/pages/viewpage.action?pageId=19631707
Thanks,
André
Comments:
SANDEEP ADE commented on 06 November 2019
below are the lines from alm end
defect.summary = replica.summary
//defect.description = replica.description
defect.attachments += replica.addedAttachments
defect.attachments -= replica.removedAttachments
defect.commentsArea = commentHelper.mergeCommentsIntoCommentsArea(defect, replica)
defect.status = qcHelper.getStatus(replica.status?.name)
and below are the lines from Jira
StatusSync.receiveStatus(
true,
[
“Open”: “Requested”,
“Approved” : “Approved”,
],
replica,
issue,
nodeHelper
)
