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 can we copy only the date part from two Date Time Picker custom fields (Actual Start and Actual

Beeramgunta Saivinay_t5pynm

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?

Accepted answers

Trudy P Claspill

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?

All comments

Trudy P Claspill

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/

Beeramgunta Saivinay_t5pynm

Thanks for your responce.

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

Trudy P 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_t5pynm

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

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud