Bulk changing due dates

[Ian Rickwood]

Hi,

Currently working with Free Jira and wish to push back and entire project plan by 30 days for various reasons.

I can't seem to do this with bulk change as the date is fixed and I want variable, which the field in Edit Issues won't accept.

I believe it is possible in Global automation and have set the rule to apply to the specific project but cannot get it to run across all issues, only one at a time with a manual trigger. This is OK but I believe it possible to change the entire project with scheduled automation. This however keeps telling me I need a branch but not what the branch requires so I am a bit stuck.

My statement in the rule is {{issue.duedate.plusdays(30)}}

Any help would be appreciated as it is a huge timesaver for me

Ian

[Staffan Redelius · Accepted solution]

Hi @Ian Rickwood 

I think i found a working solution for you:

1.  Create a trigger "When: Scheduled"  set End date to "One occurence" and add a JQL i.e.  "project = XXX and duedate is not empty" so you filter out the issues you want to update.
2. Add a FOR EACH branch and select "Current work item"
3. Add a THEN step and choose to update the field "Due date" and paste your smart value {{issue.duedate.plusdays(30)}}
4. Set the date and time for when the trigger should fire and update the rule

I would recommend to test the rule for a small number of issues first and validate the functionality (narrow down the JQL to only include a few issues).

The rule would look something like this:

Let me know if it helps!

Best regards,
/Staffan

[Ian Rickwood]

Hi Staffan,

It works when I put {{project.Test}} as the statement in the trigger for the rule but the branching you gave me helped a lot, thank you.

I am able to shift my projects out as desired, thanks again to the community.

Ian R

[Evgenii · Accepted solution]

Hi, @Ian Rickwood 

You can create a scheduled automation rule that selects issues using a specific JQL query and performs an action for each of them.

The key part is crafting the right JQL — it should accurately target only the issues you want to include in the automation.

[Ian Rickwood]

Thanks Evgenii,

That was the last piece of my puzzle, thank you, I will try that out.

Ian R

[Alexander Hohmann · Accepted solution]

An automation rule will only apply to the current work item. So you need to crate a branch and make it for all items related to the current one in some form (parent, child, created by this one etc.)

Have you considered the alternative of exporting all the issues into a CSV for Excel, edit them in a spreadsheet and then re-import only the required columns, i.e. item keys / issue keys and date? The import will overwrite the existing dates.

[Alexander Hohmann]

Sorry, I should have added that an automation rule will apply only to the current item if manually triggered. You could however have a 'scheduled' trigger and then have the rule run over all items in a project.

[Ian Rickwood]

Thanks Alexander,

I hadn't considered the export method, thanks, I will give it a go.  This however means setting up a new project as you go through the CSV import process, presumably discarding the old one into the trash.

The rule would become very complex as I have a more waterfall project plan if my understanding is correct.

Thanks again,

Ian R

[Ian Rickwood]

Hi Alexander,

Your second answer is the solution I have been having issues with. I cannot get the scheduled rule to validate as it seems to want branches, which I don't understand.

Are you aware of any examples of using a scheduled automation to change all the due dates in this way?

Ian R