nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Automate due date in Dependency in Advanced roadmap

Spartans

Hi Team,

My question is about the dependency due date changes.

For Example:

I have a project with 3 stories with some dates.

1. Test-1 - 17th Jul- 31st Jul

2. Test-2 - 1st Aug - 16th Aug

3. Test -3 - 17th Aug - 31st Aug

Now If "TEST-1" cannot be completed in time and takes 1 day extra. (i.e., completes on 1st Aug). I need the "TEST-2" task to be automatically changed to 2nd Aug - 17th Aug and the Third should start on with 18th Aug - 1st Sep.

I have a Json Script for it

{

"cloud": true,

"rules": [

{

"id": 13092381,

"clientKey": "72b7eade-078c-35bf-97f4-c86e09f1ac1b",

"name": "Update start date",

"state": "ENABLED",

"description": "",

"authorAccountId": "61d7fc9df3037f0069298117",

"actor": {

"type": "ACCOUNT_ID",

"value": "557058:f58131cb-b67d-43c7-b30d-6b58d40bd077"

"created": 1686816633939,

and so on........,

But I'm Unable to apply this rules in Automation, since I don't know more sure of (When , Condition and Then to use ) or is there any simple rule for automating the above one.

If there, please help me with the solution with a Screenshot of automation rules.

Accepted answers

All comments

Trudy P Claspill

Hello @Spartans

You have said that you are using Advanced Roadmaps, but you have also tagged your post as being for the Free version of the product. The Free version of the product doesn't include Advanced Roadmaps.

Are you using a Trial or Paid subscription of the Premium product?

You can use auto-scheduling in AR to automatically adjust dates on dependent issues, but it will adjust other issue dates also.

If you don't want to use auto-scheduling, then you can adjust dates through Automation Rules with a rule like this:

Screen Shot 2023-07-14 at 12.31.57 PM.png

However, what you end up creating is a rule that detects a change made by a previous execution of the same rule, and causing the rule to be called again for a new issue. There is a limit to how many times Jira allows that to happen, and that limit is 10. If you had a chain of dependencies of more than 10 issues, the Automation Rule would not be able to update all of the dependent issues.

Spartans

The Screenshots are from my organizational account and I'm using this account for asking community so that I can have a look.

Okay then is there any other ways to make it happen.
Also this is the full code.

{

"cloud": true,

"rules": [

{

"id": 13092381,

"clientKey": "72b7eade-078c-35bf-97f4-c86e09f1ac1b",

"name": "Update start date",

"state": "ENABLED",

"description": "",

"authorAccountId": "61d7fc9df3037f0069298117",

"actor": {

"type": "ACCOUNT_ID",

"value": "557058:f58131cb-b67d-43c7-b30d-6b58d40bd077"

"created": 1686816633939,

"updated": 1687165052244,

"trigger": {

"id": "277076674",

"component": "TRIGGER",

"parentId": null,

"conditionParentId": null,

"schemaVersion": 2,

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

"value": {

"changeType": "ANY_CHANGE",

"fields": [

{

"value": "duedate",

"type": "field"

}

"actions": []

"children": [],

"conditions": [],

"connectionId": null

"components": [

{

"id": "277076675",

"component": "BRANCH",

"parentId": null,

"conditionParentId": null,

"schemaVersion": 1,

"type": "jira.issue.related",

"value": {

"relatedType": "linked",

"jql": "",

"linkTypes": ["blocks"],

"onlyUpdatedIssues": false,

"similarityLimit": 40,

"compareValue": 0

"children": [

{

"id": "277076677",

"component": "ACTION",

"parentId": "277076675",

"conditionParentId": null,

"schemaVersion": 10,

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

"value": {

"operations": [

{

"field": {

"type": "NAME",

"value": "number"

"fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:float",

"type": "SET",

"value": "{{Start date.diff(triggerIssue.Due date).days.plus(1)}}"

}

"advancedFields": null,

"sendNotifications": true

"children": [],

"conditions": [],

"connectionId": null

{

"id": "277076681",

"component": "ACTION",

"parentId": "277076675",

"conditionParentId": null,

"schemaVersion": 10,

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

"value": {

"operations": [

{

"field": {

"type": "NAME",

"value": "Start date"

"fieldType": "com.atlassian.jira.plugin.system.customfieldtypes:datepicker",

"type": "SET",

"value": "{{triggerIssue.Due date.plusBusinessDays(1)}}"

}

"advancedFields": null,

"sendNotifications": true

"children": [],

"conditions": [],

"connectionId": null

}

"conditions": [],

"connectionId": null

}

"canOtherRuleTrigger": true,

"notifyOnError": "NEVER",

"projects": [],

"labels": [],

"tags": [

{

"id": 34758869,

"tagType": "IS_RULE_UPDATED",

"tagValue": "true"

}

"ruleScope": {

"resources": ["ari:cloud:jira:d9259933-1e47-443b-9b58-a49f30db7476:project/10001"]

"writeAccessType": "UNRESTRICTED",

"collaborators": [],

"billingType": "NORMAL"

}

]

}

Will this be able to make any changes ?

Trudy P Claspill

I prefer to look at rules based on the UI display rather than slogging through JSON code.

If you'd like to provide screen images of that, I'll review it.

Or, you can simply try out your rule against test issues and see what it does.

Spartans

I tried with your automations, but its getting failed on condition and you were also that it will not be applicable for more dependencies. So I was thinking for a better resolution from you.

I had received a code from a person stating that this would work, but I'm unable to do the automation, where to paste the code.

Is there any other ideas that can do the dependency mapping on due date linked with other start date as above ?

I tried with used cases, YouTube but unable to find a best resolution.

But its not working.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management