Jira Automate Identify If a Component Has been Removed

[Daniel Lupton]

I have a use case where if a component is removed from an issue we want to remove the component from all child issues.

I have been able to use {{#changelog.components}}{{toString}}{{/}} to identify is a component has been added to an issue BUT I cannot find a way to identify if the component has been removed as the removed components are not in the change log that I get form this.

Does anyone have any ideas on how we can identify if a component has been removed from an issue?

[Kristian Walker _Adaptavist_ · Accepted solution]

Hi Joana,

Thank you for your question.

I can confirm that when importing a complete project with issue data and attachments that Project Configurator uses the built-in Jira data import functionality which Jira Provides out of the box and that this functionality mandates that a project must be empty before data can be imported into it.

This means that like Alexy, said in the previous comment that you would need to delete the original project before you will be able to re-run the data import.

If the target instance already contains a project with the same key that is a different project then you will need to rename the Project in the source instance to have a new unique key which does not exist inside the target instance before generating a new export to import from. 

You can see further details on the process for importing a complete project inside of the documentation page located here.

If this response has answered your question can you please mark it as accepted so that other users searching for a similar question can see that this is a correct answer.

Regards,

Kristian

[itsupport]

Hi Kristian,

We are also facing the same issue and if I try with new key in source machine before export, it is throwing an error, like there is no project with mentioned key and you can try with creating new project with CUST key.

Can you help me on the same ASAP.

[Kristian Walker _Adaptavist_]

Hi Instancy,

We notice that you have raised this same question in your support ticket through the Project Configurator support portal and we can confirm that we are dealing with your question through the support portal.

Regards,

Kristian

[Alexey Matveev · Accepted solution]

Hello,

Before import a project to an existing project, you should delete all issues from the project, where you want to import your data.

[itsupport]

I was verified that, there is no issues exist in my service desk project but it's still throwing an error after re-indexing.

No projects left to import. Project(s) CUST will not be imported because they exist and are not empty in this JIRA instance