Automation of Stories and CLONEs

[Cyril James]

Hello Friends, I have automation set up so that when someone creates a new story, the story description is pre-populated with the info for required information that is needed to groom the story.  Acts like a story template. 

However, if we take an existing story and CLONE it, the existing story description is erased and replaced with the pre-populated description from a template so we are starting form scratch.

How can we exclude the pre-populated story description when cloning.

Thank you!

[ASweeten · Accepted solution]

Hi Yogesh,

It looks like Clarizen allows you to export data to a CSV file using the Data Warehouse Export tool.  The Amazon S3 export appears to output a flat file which should allow you to import your data into JIRA: 

- Amazon S3 (as a flat file, e.g. CSV, JSON)
  Flat files must first be saved to Amazon S3, then downloaded locally if needed.

I don't have a lot of confidence that your workflows will be importable in this manner.  You will likely need to rebuild them.  Here is the workflow documentation to get you going.

[Yogesh Mude]

HI @ASweeten,

Thanks for the response.

Yes, we can export the data to a .csv file from Clarizen and I have prepared the file as we want I tried to import in Jira using CSV import in jira and it works perfectly.