Due Date automations based on labels

[Candice Gerard]

Two days in with no result to show, and feeling quite stupid. 

1 - I am using labels values of day counts -90 days to 45 days. 

2- I want to make a global automation for my projects that look for changes in due date on issues with a "0" value as a label. 

3- If there are changes to the due date to that item, I would like due dates for the rest of the project items to be updated with that due date MINUS the number value held in their own label.    For examples, I change the due date on my 0 items to 5/30/2023, all due dates of other non completed items with a labels value of 30 should change to 4/30/2023.  

Currently, I can get all the due dates to update to NULL. when triggered by my 0 item,,  which is not helpful.    Is anyone willing to help this total noob at Jira?  I would really appreciate it.  

[Timothy]

open a templated email on outlook to respond to their issue

Hmm, isn't canned responses what you're looking for?

• https://www.atlassian.com/blog/jira-service-desk/get-time-back-canned-responses-sla-copy-configurations-jira-service-desk-server

Your end users will still come back to your Service Desk and respond to you there.

route the issue toward someone on our dev team

As for this part, you can create a issue in the dev teams project and use automation to transition requests when the dev team's issue is transitioned.

• https://confluence.atlassian.com/servicedeskcloud/automating-your-service-desk-732528900.html

[Raphael]

Hmm, isn't canned responses what you're looking for?

Not canned per-se. My template has a standardized subject line with the issue number, and the date that their issue was submitted. It also includes a recap of the issue they're having, and sometimes specific questions to get more information or clarification. It varies with each issue submitted. In that sense, canned responses wouldn't be ideal.

I'm ideally looking for something akin to how commenting on tickets work now: sharing the comment with a customer, or internally.

As for this part, you can create a issue in the dev teams project and use automation to transition requests when the dev team's issue is transitioned.

I'll take a look at this, thanks!