• Type: Bug
• Resolution: Fixed
• Priority: Low
• Fix Version/s: 3.3.0
• Affects Version/s: 3.2.0
• Component/s: Automation
• Labels:

  • affects-cloud
  • affects-server

[JSDSERVER-4357] Automation: JQL Linked issue if condition accesses outdated data

Collapse comment: Olivier added a comment - 03/Nov/2016 10:34 AM, Edited by Olivier - 03/Nov/2016 10:35 AM

Olivier added a comment - 03/Nov/2016 10:34 AM - edited

+1

This is a real problem and now we can not use service desk in our company.

It is very important to ba able to create a rule that behaves like:

WHEN (A linked issue is transitioned)
IF (Linked issue matches "status=Closed")
THEN (Transition issue)

This rule should fire when the linked issue transitions TO Closed, but actually it is not working it is FROM Closed.

How will it possible to create an automation when a linked issue is closed...the status change TO close or the resolution changed TO not empty) ?

Expand comment: Olivier added a comment - 03/Nov/2016 10:34 AM, Edited by Olivier - 03/Nov/2016 10:35 AM

Olivier added a comment - 03/Nov/2016 10:34 AM - edited +1 This is a real problem and now we can not use service desk in our company. It is very important to ba able to create a rule that behaves like: WHEN (A linked issue is transitioned) IF (Linked issue matches "status=Closed") THEN (Transition issue) This rule should fire when the linked issue transitions TO Closed , but actually it is not working it is FROM Closed . How will it possible to create an automation when a linked issue is closed...the status change TO close or the resolution changed TO not empty) ?

Collapse comment: jozacks added a comment - 20/Oct/2016 10:20 PM

jozacks added a comment - 20/Oct/2016 10:20 PM

Just to be clear, the automation rule that I'm seeing this problem (100% of the time for me) is a preset rule that JIRA automatically creates in any new IT Service Desk project (it's not a custom rule I setup, and I didn't alter it in any way).

Expand comment: jozacks added a comment - 20/Oct/2016 10:20 PM

jozacks added a comment - 20/Oct/2016 10:20 PM Just to be clear, the automation rule that I'm seeing this problem (100% of the time for me) is a preset rule that JIRA automatically creates in any new IT Service Desk project (it's not a custom rule I setup, and I didn't alter it in any way).

Collapse comment: Eric Franklin (Inactive) added a comment - 20/Oct/2016 8:21 PM, Edited by Eric Franklin - 20/Oct/2016 9:36 PM

Eric Franklin (Inactive) added a comment - 20/Oct/2016 8:21 PM - edited

Another example of this we've found is this:

Steps to Reproduce

1. Create an automation rule with following components
   1. When linked issue transitioned
   2. If linked issue matches status = "Resolved"
   3. Then Comment on issue
2. Create an issue and link it to an issue in another project
3. Transition linked issue to Resolved

The issue will not receive a comment until the linked issue transitions outside of the 'Resolved' status. This is not ideal, as users often would like to have comments on other related issues indicating that a parent issue might have been resolved.

UPDATE: A customer and I have tested thoroughly in both his instance and my test instance. This seems to happen consistently, so I have raised the affected users field to 75% (since I can't determine if it happens 100% of the time).

Expand comment: Eric Franklin (Inactive) added a comment - 20/Oct/2016 8:21 PM, Edited by Eric Franklin - 20/Oct/2016 9:36 PM

Eric Franklin (Inactive) added a comment - 20/Oct/2016 8:21 PM - edited Another example of this we've found is this: Steps to Reproduce Create an automation rule with following components When  linked issue transitioned If  linked issue matches status = "Resolved" Then Comment on issue Create an issue and link it to an issue in another project Transition linked issue to Resolved The issue will not receive a comment until the linked issue transitions outside of the 'Resolved' status. This is not ideal, as users often would like to have comments on other related issues indicating that a parent issue might have been resolved. UPDATE: A customer and I have tested thoroughly in both his instance and my test instance. This seems to happen consistently, so I have raised the affected users field to 75% (since I can't determine if it happens 100% of the time).