Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,465,895
Community Members
 
Community Events
176
Community Groups

Jira Automation does not work for Service Project

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?

2 answers

1 vote
Jack Brickey Community Leader Jul 01, 2022

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.

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": []

}

]

}

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.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events