Idea ID: 2875544

Detect synced jira items whitch are moved to another jira project at a later time or deleted in jira

Status: Waiting for Votes

If synced jira items are moved to another jira project at a later time or deleted in the jira project, this is not detected by the MF Connect sync

MF Connect should provide a mechanism or script that matches Octane items and Jira items and creates a list of the items that are not included in Octane and Jira. And send this list to a email adress whitch can be defined by a MF Connect administrator.

Parents
  • I think it's good that "orphaned" octane entities aren't generally deleted. Because there could be other entities linked to them, for example manual tests. If orphaned entities were automatically deleted, this would complicate the decision of how to deal with the entities that had previously referenced the orphaned entities. A list of orphaned entities would allow the user to decide how to deal with the orphaned entities on a case-by-case basis. It would be helpful if orphaned entities were marked in Octane itself via a corresponding field because this field could be evaluated explicitly using filters.

Comment
  • I think it's good that "orphaned" octane entities aren't generally deleted. Because there could be other entities linked to them, for example manual tests. If orphaned entities were automatically deleted, this would complicate the decision of how to deal with the entities that had previously referenced the orphaned entities. A list of orphaned entities would allow the user to decide how to deal with the orphaned entities on a case-by-case basis. It would be helpful if orphaned entities were marked in Octane itself via a corresponding field because this field could be evaluated explicitly using filters.

Children
No Data