We had two issues on our JIRA board that had the same key (MKT-2436). When selecting one, it would display the other (the "original" worked without issue). I deleted the "original" and now the duplicate issue is sitting in the backlog and can't be moved, deleted, edited, etc.
When selecting it, a red error dialog appears "Error Issue does not exist" and the URL http://jira..../MKT-2436 says the issue does not exist.
In a post function script, I use a cloneissue function to create a new issue. But in a script on workflow associated to the new issue, the getKey() property returns the same key than the parent.
In database, the issuenum is different, but I can't access to the real key of new issue.
Any idea ?
thanks in advance.
This has nothing to do with this 5 year old question. I'd suggest you ask a new one to get some visibility across the community.
However, at a glance, as you're running the code in a transition, getKey is going to return the key of the current issue, not the one you are trying to create (and you can't know the key of that until after it is created, after the end of the transition)
We're looking for participants for a workshop at Atlassian! We need Jira admins who have interesting custom workflows, issue views, or boards. Think you have a story to sha...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG