• Type: Bug
• Resolution: Fixed
• Priority: Low
• Fix Version/s: 3.9.0
• Affects Version/s: 3.3.0
• Component/s: Create Request, SLA
• Labels:

  • affects-cloud
  • affects-server

[JSDSERVER-4743] Webhook triggered by Issue Creation is not sent when JQL filter users SLA fields

set-jac-bot made changes - 22/May/2020 8:11 AM

Fixed in Enterprise Release/s

New: [Download 3.9|https://confluence.atlassian.com/enterprise/atlassian-enterprise-releases-948227420.html]

Owen made changes - 27/Mar/2019 5:47 AM

Workflow	Original: JSD Bug Workflow v5 - TEMP [ 2305360 ]	New: JAC Bug Workflow v3 [ 3126455 ]
Status	Original: Done [ 10044 ]	New: Closed [ 6 ]

Owen made changes - 24/Oct/2018 5:24 AM

Symptom Severity

Original: Minor [ 14432 ]

New: Severity 3 - Minor [ 15832 ]

Morgan Knicely (Inactive) made changes - 30/May/2018 2:54 PM

Description

Original: {panel:bgColor=#e7f4fa}   *NOTE:* This bug report is for *JIRA Service Desk Server*. Using *JIRA Service Desk Cloud*? [See the corresponding bug report|http://jira.atlassian.com/browse/JSDCLOUD-4743].   {panel} h3. Summary Webhook based on JQL does not trigger when SLA fields are used and the event set to fire the Webhook is the Issue creation event. h3. Environment Cloud h3. Steps to Reproduce # Create a SD project # Set a webhook based in JQL like this: {code} "Time to first response" = withinCalendarHours() and project = XYZ. {code} Set so the webhook will be triggered in the creation issue event. h3. Expected Results The webhook is fired when an issue is created in the service desk if during the working hours in the calendar applied. h3. Actual Results The webhook is never fired.   h3.Workaround No workaround, but the user may try to manipulate the date of issue creation in the JQL to meet its criteria: {code} created > date and created < date {code}

New: {panel:bgColor=#e7f4fa}   *NOTE:* This bug report is for *JIRA Service Desk Server*. Using *JIRA Service Desk Cloud*? [See the corresponding bug report|http://jira.atlassian.com/browse/JSDCLOUD-4743].   {panel} h3. Summary Webhook based on JQL does not trigger when SLA fields are used and the event set to fire the Webhook is the Issue creation event. h3. Steps to Reproduce # Create a SD project # Set a webhook based in JQL like this: {code} "Time to first response" = withinCalendarHours() and project = XYZ. {code} Set so the webhook will be triggered in the creation issue event. h3. Expected Results The webhook is fired when an issue is created in the service desk if during the working hours in the calendar applied. h3. Actual Results The webhook is never fired.   h3.Workaround No workaround, but the user may try to manipulate the date of issue creation in the JQL to meet its criteria: {code} created > date and created < date {code}

Morgan Knicely (Inactive) made changes - 30/May/2018 2:54 PM

Summary

Original: Webhook based on JQL does not trigger when SLA fields are used

New: Webhook triggered by Issue Creation is not sent when JQL filter users SLA fields

Delan Azabani (Inactive) made changes - 29/Mar/2018 2:37 AM

Link

Original: This issue has a regression in JSDSERVER-5730 [ JSDSERVER-5730 ]

Delan Azabani (Inactive) made changes - 29/Mar/2018 2:37 AM

Link

New: This issue causes JSDSERVER-5732 [ JSDSERVER-5732 ]

Delan Azabani (Inactive) made changes - 29/Mar/2018 2:37 AM

Link

New: This issue causes JSDSERVER-5730 [ JSDSERVER-5730 ]

Delan Azabani (Inactive) made changes - 28/Mar/2018 7:19 AM

Link

New: This issue has a regression in JSDSERVER-5730 [ JSDSERVER-5730 ]

moofoo (Inactive) made changes - 16/Nov/2017 11:59 PM

Resolution		New: Fixed [ 1 ]
Status	Original: Awaiting Release [ 11372 ]	New: Done [ 10044 ]

Load more older events