How to detect if an issue is a clone in a listener at issueCreated

[Brian Louks]

Doesn't look like there's a good way to detect what's a clone via a listener. The "Cloners" issue link apparently isn't added at the time the issueCreated event is handled by the listner.

Anyone know is there's a way to detect cloning at issue create time?

[Dieter · Accepted solution]

You could check if you find some method specific to the clone action in you stacktrace. Just add this statement to your listener: new Exception().printStackTrace() and check catalina.out

[Brian Louks]

You're crazy man. I like you, but you're crazy. This does show up in the stack trace:

CreateIssueDetails.java com.atlassian.jira.web.action.issue.CreateIssueDetails createIssue

I don't want to do it ... but I just might! Thanks

[Dieter]

Well, i don't mind to be crazy if it helps ;) ... Like here: https://answers.atlassian.com/questions/37167/jira-notify-on-email-ticket-creation

[Brian Louks]

Whoops, I mean this is in the stack trace:

CloneIssueDetails.java com.atlassian.jira.web.action.issue.CloneIssueDetails doExecute

The other line I mentioned was in the stack trace, but wouldn't be very useful.

Thanks again

[francis]

Brian,

Did you find a working solution?

Francis

[Brian Louks]

I did not find any good ways to do this, no

[vinit k shah]

Hi Brian,

we also get this line in stacktrace. 

CloneIssueDetails.java com.atlassian.jira.web.action.issue.CloneIssueDetails doExecute

But My question, how we do get source jira issue Id from which cloned happen in jira event listener ? 

[francis]

Hi Vints

Check the comments below.  The way we solved it in the table grid editor app is by creating a new custom field 'Origin ID'  More information in the link

https://wiki.idalko.com/x/nYP4B

Francis

[vinit k shah]

Thanks for quick reply. 

But we don't have provision to introduce new custom fields in jira, Is it possible with some other way ? 

Actual Problem : we are add-on vendor (Test Management) , when customer uses jira's clone functionality, our data (steps) are not copied on newly created jira issue.

[Nathon Fowlie]

Resurrecting an old post, but you could look at the issue links and check the outward description. Here's some sample code. I haven't tested it so it may not compile.

Issue issue = event.getIssue();
IssueLinkManager issueLinkManager = ComponentAccessor.getIssueLinkManager();
IssueLinkTypeManager issueLinkTypeManager = ComponentAccessor.getComponent(IssueLinkTypeManager.class);

// Alternatively you could put the "Cloners" issue link type id in a constant rather than try 
// to find it by name and assuming the first list result is the one you want.
List<IssueLinkType> clonersIssueLinkTypes = issueLinkTypeManager.getIssueLinkTypesByName("Cloners");
Long cloneIssueLinkTypeId = null;

if (clonersIssueLinkTypes) {
    cloneIssueLinkTypeId = clonersIssueLinkTypes.listIterator().next().getId();
} else {
    LOG.warn("Unable to find the 'cloners' issue link type, cannot continue...");
    return; 
}

List<IssueLink> outwardLinks = issueLinkManager.getOutwardLinks(issue.getId());

if (outwardLinks) {
    for (IssueLink issueLink : outwardLinks) {
        if (issueLink.getIssueLinkTypeId() == cloneIssueLinkTypeId ) {
            // This is a cloned issue, do things and stuff.
        }
    }
}

[francis]

We actually solved it this way

http://wiki.idalko.com/display/TGPD/Behind+the+scenes+of+gd.initFromClone

Still I think this should be part of the core product.

[Nathon Fowlie]

That's a good way to handle it. I ended up doing pretty much the exact same thing. On issue created, if "OriginID" is null, this is a brand new issue so set OriginID to the issue key of the newly created issue. If not null, then this is a clone of an existing issue, do whatever needs to be done and update OriginID.

[Brian Louks]

I did not find any good ways to do this, no