There should be an option in transition to require developer entering the duplicate key. We don't want to resolve issues as duplicates without entering the duplicate.

What we are looking at for an initial implementation would be to allow the 'Resolve Issue' page to redirect to the Link Issue page (or vice versa).

This will require less clicks, but will still require two pages.

We think that we can get this initial implementation done in the next version.

We should also consider another checkbox which will automatically resolve the issues linked here as duplicates.

What is the status of this issue? In PDF documentation is written (Chapter 3.1.4 "Resolutions"):

Duplicate

The problem is a duplicate of an existing issue. Marking an issue duplicate requires the
issue# of the duplicating issue and will at least put that issue number in the description
field.

But when I click to "resolve issue" or "close issue" and select resolution "Duplicate", there is no way to add issue, which is duplicated by current issue.

Jozef - I think what the documentation is suggesting is that the user who is resolving it as a duplicate enter the issue key of the duplicate in their comment when resolving. That description you're quoting is simply a default that may come shipped with the system, and is customized by the administrator for each site (in Admin / Resolutions). Mine certainly doesn't say that. Some sites (like this one) have also set up a duplicate Link type, but that's optional.

Jozef,

As Neal accurately pointed out the documentation is misleading. The documentation is getting at the fact that "it is a good idea" to mentioned the issue# when resolving an issue as a duplicate. A better way is to define a 'duplicate' issue link and link the issues.

We will fix the documentation.

This issue will actually be addressed when we implement JRA-6748. It will be possible to link issues as they are being resolved. We will try to implement JRA-6748 in JIRA 3.6, but I cannot promise this with any certainty.

Thanks,
Anton

Please don't forget about this case! Closing cases as duplicates is something you do often and regularly, and the ability to have a formal way to assert that a link to an existing case is specified seems a very natural feature for Jira.

I am currently evaluating Jira and this issue seems to be a major deficiency when compared with Bugzilla. We need to be able to "Resolve as Duplicate" where state becomes resolved, resolution becomes duplicate and the required link is created.

We are about to transfer our Bugzilla users to the Jira environment, and this is one of the requirements.
It would be nice to be able to create a screen in which you can select the LINK field from the LINK ISSUE window.
Thus, this screen could be chosen as TRANSITION VIEW when defining e.g. a transition 'Mark as duplicate', destination step Closure.

This was suggested by the users on our install (see comments on https://jira.secondlife.com/browse/WEB-401 ). This would be a really good productivity boost for us.

In the same way that you have a link type (defaulted to Cloners) in properties file to automatically create links when cloning an issue, you can have properties that define
a) the link type
b) the resolution type(s)
So, when an issue is resolved with type specified, and a link type specified in properties exists, that it links the two automatically.

This is something that has been supported by Bugzilla for some while; the "Mark the bug as duplicate of bug #" option has a box next to it for the other bug number.

Please fix this soon!

We moved from Bugzilla (where we had this feaure) to Jira (where we don't). The lack of this feature is driving us crazy!

What is considered "short term roadmap" (=current status) by Atlassian. It is put in that state on Apr 29, 2009. Will this still be delivered in a 3.13 point release or will this be 4.0 beta?

Hi,

This issue will not be in either of these releases as the JIRA 3.13.x releases contain only bug fixes, while 4.0 release is already full of other features.

Placing issues onto a Short Term Roadmap does not indicate a version, but our intentions to try and implement it within the next few major releases. Please note, that while we do our best, it is not a guarantee.

Cheers,
Anton