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

Why does Jira copy over Cycle Start Date-time and Cycle Ends Date-time when cloning an issue?

Dave Butler_z95ks2

Why does Jira copy over Cycle Start Date-time and Cycle End Date-time when cloning an issue? This makes no sense to me. Just like it would not make sense to copy Issue Status when cloning. Cloned Cycle Start Date-time values, if not removed by the person cloning, can severely skew cycle time metrics.

Is there some virtue to cloning Cycle Start Date-time and Cycle End Date-time?

Is there any chance Atlassian will change Jira to not clone Cycle Start Date-time and Cycle End Date-time?

Is there any way that we can configure Jira on our end to prevent the cloning of Cycle Start Date-time and Cycle End Date-time?

Thanks,
Dave

Accepted answers

Bill Sheboy

Hi, Dave -- Welcome to the Atlassian Community!

Those are not built-in fields, and are likely custom fields added by your Jira admin(s) or by a marketplace addon app. So first thing, I would identify the purpose of those fields.

If they were added by a Jira admin, you may need to either manually clear them or use an automation rule to do so.

If they were added by an addon, there may be a problem if they are not cleared for cloning. The addon vendor could help with that.

Kind regards,
Bill

All comments

Bill Sheboy

Hi, Dave -- Welcome to the Atlassian Community!

Those are not built-in fields, and are likely custom fields added by your Jira admin(s) or by a marketplace addon app. So first thing, I would identify the purpose of those fields.

If they were added by a Jira admin, you may need to either manually clear them or use an automation rule to do so.

If they were added by an addon, there may be a problem if they are not cleared for cloning. The addon vendor could help with that.

Kind regards,
Bill

Dave Butler_z95ks2

Thank you very much, Bill. I'll ask our admin folks.

Dave Butler_z95ks2

Hi @Bill Sheboy,

Actually, I just checked and found that I'd misstated those names. The fields I intended to ask about are Cycle Time Start and Cycle Time End.

Does that change your answer?

Thanks again,

Dave

Bill Sheboy

Nope: my understanding is there are no built-in fields for cycle times, lead time, and other such process flow measurements (e.g., WIP, age of WIP, etc.).

Instead there is a built-in, interpretation of a control chart for boards to show such measures. But those are only viewable by looking at the report and hovering over issues...and there are many challenges with that report.

And so...teams either add fields like you note (with automation rules to fill them) or use a marketplace addon.

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