How can we copy only the date part from two Date Time Picker custom fields (Actual Start and Actual

[Beeramgunta Saivinay]

We have two custom fields: Actual Start and Actual End, both of type Date Time Picker. These field types are not supported in Jira Plans.

Since we need to include these fields in Jira Plans, and we cannot change their field type, we created two new fields: Actual Start 1 and Actual End 1, both of type Date Picker.

Our requirement is to copy only the date portion from Actual Start and Actual End to the corresponding Actual Start 1 and Actual End 1 fields.

How can we copy only the date part from two Date Time Picker custom fields (Actual Start and Actual End) to two Date Picker fields (Actual Start 1 and Actual End 1) so they can be used in Jira Plans?

[Trudy Claspill · Accepted solution]

Hello @Beeramgunta Saivinay 

You could accomplish that with Automation Rules functionality. Are you familiar with that functionality?

https://support.atlassian.com/cloud-automation/docs/jira-cloud-automation/

Is this a task that you will need to keep doing for new issues? Or do you need to do it only for existing issues, after which you will stop using the date/time fields and go forward using the date-only fields?

[Beeramgunta Saivinay]

Thanks for your responce.

This requirement for existing issues. once copied data old to new, data & time type is optional.

[Trudy Claspill]

How many issues do you need to process?

As I mentioned, you could do this with Automation Rules. There are limits to the number of issues that can be processed in a single run of an Automation Rule.

https://support.atlassian.com/cloud-automation/docs/automation-service-limits/

There are also limits to the number of Automation Rules that can be executed within a month.

https://support.atlassian.com/cloud-automation/docs/how-is-my-usage-calculated/

Are you familiar with Automation Rule construction? Do you need more specific guidance on how to construct a rule for this purpose?

[Beeramgunta Saivinay]

Yes, I have good knowledge on Automation. but not working on Old issues, but automation is working on edit issue one by one. i need at a time run 67 issues(Our requirement having 67 issues).

Regards,

Sai

[Trudy Claspill]

You can create an Automation rule that uses the Schedule trigger, and provide a JQL that will select the 67 issues. Then add an Edit action that would copy the data to the appropriate fields. The Edit action will run against each issue found in the JQL you put into the Schedule trigger.

https://support.atlassian.com/cloud-automation/docs/jira-automation-triggers/#Scheduled

[Beeramgunta Saivinay]

I created the automation rule but not working. pls suggest me.

[Trudy Claspill]

In what way is the rule not working?

What are the results you observe in the issue?

Please provide a screen image that shows the output in the rule audit log for the execution of the rule. Make sure you expand all the sections.

In your automation you are checking a field named "t2"

In your Edit action you're using JSON in the edit action to copy from customfield_10158 to custofmield_10157, and clear the field "t2".

Is one of those two custom fields "t2"?