Jira Automation does not work for Service Project

Question

I have a global Jira automation rule that sets an issue's due date based on the start date of the release specified in the "Fix Versions" field.

This automation works fine for all of our "Software Projects". However, it does not appear to work for our "Service Project".

When setting the "Fix Versions" field of a Service Project issue, I can see that the automation triggers by looking at its audit log. The audit log claims "Field values changed MYPROJ-123". But when I reload that issue, the "Due Date" field is still not set.

Is this functionality not available for Service Management Projects?

Nick de Palézieux · Answer

Just now I see that for an issue in a Software Project - where I thought the automation was working fine - the audit log shows that the automation ran, but the allegedly modified issue does not have the due date set.

Nick de Palézieux · Answer

Thanks for your response @Jack Brickey here is the rule:

{

"cloud": true,

"rules": [

{

"id": 6817145,

"name": "Set due date when setting fix version",

"state": "ENABLED",

"description": null,

"created": 1656572539782,

"updated": 1656678400201,

"trigger": {

"id": "129907158",

"component": "TRIGGER",

"parentId": null,

"conditionParentId": null,

"schemaVersion": 2,

"type": "jira.issue.field.changed",

"value": {

"changeType": "VALUE_ADDED",

"fields": [

{

"value": "fixVersions",

"type": "field"

}

],

"actions": []

},

"children": [],

"conditions": [],

"connectionId": null

},

"components": [

{

"id": "129907159",

"component": "ACTION",

"parentId": null,

"conditionParentId": null,

"schemaVersion": 10,

"type": "jira.issue.edit",

"value": {

"operations": [

{

"field": {

"type": "ID",

"value": "duedate"

},

"fieldType": "duedate",

"type": "SET",

"value": "{{issue.fixVersions.startDate.minusBusinessDays(3)}}"

}

],

"advancedFields": null,

"sendNotifications": true

},

"children": [],

"conditions": [],

"connectionId": null

}

],

"canOtherRuleTrigger": true,

"notifyOnError": "FIRSTERROR",

"projects": [],

"labels": [],

"tags": [],

"ruleScope": {

"resources": [

"ari:cloud:jira::site/0093e998-e2ec-4419-9b2d-c2df9137d717"

]

},

"writeAccessType": "UNRESTRICTED",

"collaborators": []

}

]

}

Jack Brickey · Answer

Could you share your rule here? I have not used fix versions in my JSM projects but willing to test it out and see what I experience.