How to clone a Project and it's Issues?

[Luc Leermakers]

This question is in reference to Atlassian Documentation: Administering a project

How can I clone a Project and it's Issues? Goal is to let a new project and it's contents/issues/etc be an exact copy of an already existing project.

[Lisa Förstberg]

Maybe an option is to set up the SLA rules to "seem" as if it is counting down?

For example in a People Onboarding process we want to count down the days to an employee starting (date is a custom field)

Setting the goal to for example: 

issuetype = Onboarding AND "Employment Start Date" <= startOfDay("+1d") with the Goal = 24

then adding more goals

issuetype = Onboarding AND "Employment Start Date" <= startOfDay("+2d") with goal 48h 

etc 

The SLA Goal order is important. It will fire on the first rule that the issue matches, hence swapping out the goal as we close up on the Employment start date.

[Gomez, Daniel]

i would like to set a countdown timer to start when an issue goes on hold. What you are saying above sounds like this is very possible. I take it through a jql filter i can set the time to start at 3 weeks and countdown from there as long as i set the two goals like above?

[Lisa Förstberg]

I would say use the SLA trigger (not the goals section) to trigger on entered status (on hold) for that case.

[Gomez, Daniel]

how would I set the timer to start at 3 weeks and count down? Is it possible to do without a plugin?

[Lisa Förstberg]

This is my example on how I count down towards a new employee starting his/her first day.

I have a custom field for employment start date, which will start to count down if we're closing up on the first week.

[Gomez, Daniel]

this is awesome, it will also help me on a dashboard gadget. Thanks so much!

[Lisa Förstberg]

superduper - no problems! Maybe also accept my answer here on AC ;-) 

[Gomez, Daniel]

i only see the vote button

[AMAÇ SUNER]

Hi,

We have similar issues in our company. Our customers make development or bug fix requests and we commit different dates for each request (issue) instead of fixed time duration.  We put those dates as due dates of issues.

We are using Time to SLA app which enables to set custom date fields (eg. due date as in your example) as target date for an SLA. 

For example, we have an SLA defined with target date as due date. When we input some date into due date as we open an issue then SLA counts down to that date.

You can check the link below.

https://confluence.snapbytes.com/display/TTS/Defining+SLA

Look for the SLA Negotiation Date Field in the document. 

I hope that helps you solve your problem.

amac

[Ravi Sagar _Sparxsys_]

Aaron,

The default SLA in JIRA Service Desk are not based on dates but you can install "Extension for JIRA Service Desk" add-on to setup SLA based on date fields like Due date and other date type custom field.

Ravi

[Aaron Knox]

Hi Ravi, thanks for the response.

That link doesn't work for me but I have found the extension you are referring to.

https://marketplace.atlassian.com/plugins/com.intenso.jira.plugins.jsd-extender/server/overview

[Egunsuren]

Hey Aaron, have you figured out how to do this?