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; } } }

How to create rules to add date in front the summary?

Louis Lew

Hi everyone, is anyone here know how to create rules where my user fill up the due date in the ticket and automatically add the fill up due date in front my ticket summary?

Example when user select the due date let say 23 July 2024 and then when they submit the ticket then it will automatically add the due date they filled in fron the ticket summary.

Accepted answers

Christopher Yen

Ideally I would suggest convincing your users to utilize the list view/queue with the due date column next to summary.

but in terms of how to create a rule to add the date in front of the summary I believe you can do it by using placing the due date and summary smart values into the summary field when the rule triggers,

Trigger: When value changes for due date
Then: edit issue fields
Summary: {{issue.dueDate}} - {{issue.summary}}

All comments

Christopher Yen

Ideally I would suggest convincing your users to utilize the list view/queue with the due date column next to summary.

Trigger: When value changes for due date
Then: edit issue fields
Summary: {{issue.dueDate}} - {{issue.summary}}

Louis Lew

Hi @Christopher Yen it works. Thank you!

Sreenivasaraju P

Hi ,

If you append due date to the summary on each change, then all the previous due dates will concatenate in the summary.

Ex: Changed due date from 25th to 26th and to 27th, then the summary will be as follows.

2024-07-27 - 2024-07-26 - 2024-07-25 - original summary.

Louis Lew

Hi @Sreenivasaraju P so far i only have one due date.

Louis Lew

Hi @Christopher Yen how about the form field? Do you know how to append the user filled up field in the form in front the ticket summary? Thanks

Christopher Yen

is it request type? or a custom field called form?

For request type I think the smart value would be {{issue.Request Type.name}}

Custom field you'll have to find the custom field ID, you can reference this article
https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/

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