Text box for duplicate when a bug is a duplicate

[ludde]

There should be a form item for writing the bug number when you mark a ticket as a duplicate.
Developers are lazy, they tend to forget stuff, etc.
The original bug should get a notice that given bug was marked a dupe of it

[cmlenz]

Related to ticket relations (see #1242 and #31).

[cboos]

Indeed, I was thinking of having a text area for this purpose,
which would be enabled when the resolution is set to duplicate.

This text area would then contain the reference to the duplicated ticket(s)
and would create a has-duplicate relation for each referenced ticket.

I'll put that soon in the source:branches/cboos-dev/trac-obj-branch
and drop a note here when it's implemented.

[jornh]

WorkFlow#ExampleManipulator implements this based on code currently living in source:sandbox/workflow

[cboos]

I implemented that in the xref branch a while ago, but this needs to be reworked on other bases, now, so "un"-accepting the ticket for now.

[ecarter]

This could be done with a plugin that uses the WorkFlow stuff. (And would likely be a good candidate for sample-plugins/workflow.)

[David Hopwood]

#5197 has been marked (in two places, manually ;-) as a duplicate of this bug.

​http://tn123.ath.cx/TracDuplicates/ is a plugin that solves part of the problem, although this should really be built-in.

[david.goliath@…]

#6924 has been marked as a duplicate of this bug.

Because it wasn't identical, it is quoted below:

Duplicate tickets often contain valuable information.

It seems to me that when a ticket is marked as a duplicate, a link to the duplicate should be placed on the page for the primary ticket (the one it duplicates.)

Alternatively, when a ticket is marked as a duplicate, all of its information could be copied to (or, better yet, transcluded onto) the page of the primary ticket. Though this second solution seems much more complicated to implement, but might offer even better functionality than just linking.

[trac@…]

We are beginning to use trac as a replacement for Bugzilla as we like the fact trac integrates so nicely with svn and like the wiki features too.

This is the one feature I miss from bugzilla. Will try the plugin though.

[ecarter]

I just added an xref operation to ​wiki:AdvancedTicketWorkflowPlugin that can be used to implement the original reporter's request.

[cboos]

#7421 closed as duplicate.

Moving this to experimental, as it's not 1.0 anymore (could well be wontfix because a plugin solution exist, or revived to be included in Trac's base ticket system in a later release).

[cboos]

#8065 closed as duplicate.

[cboos]

Milestone experimental deleted

[cboos]

See comment:15.

[david-sarah@…]

Please reconsider the closing of this ticket.

This bug had four duplicates (#5197, #6924, #7421, #8065), suggesting that it should be considered basic functionality and supported by default. I consider this a glaring omission in Trac compared to most comparable bug tracking systems.

The two plugins mentioned do not adequately implement the requested functionality:

• The ​TracDuplicates plugin does not indicate the duplicate bug(s) (in either direction) in the bug header.

• The ​TracHacks:wiki:AdvancedTicketWorkflowPlugin is complicated by many options irrelevant to duplicates, and the documentation of the xref option comes with the disclaimer "Note that the implementation of this operation is not robust."

[cboos]

Replying to david-sarah@…:

Please reconsider the closing of this ticket.

Thanks for your well documented analysis.

This bug had four duplicates (#5197, #6924, #7421, #8065), suggesting that it should be considered basic functionality and supported by default. I consider this a glaring omission in Trac compared to most comparable bug tracking systems.

This is indeed a good indicator, but sometimes even in this case the feature could be provided as a plugin, or as an optional component that we could bundle in tracopt.

The two plugins mentioned do not adequately implement the requested functionality:

• The ​TracDuplicates plugin does not indicate the duplicate bug(s) (in either direction) in the bug header.

• The ​TracHacks:wiki:AdvancedTicketWorkflowPlugin is complicated by many options irrelevant to duplicates, and the documentation of the xref option comes with the disclaimer "Note that the implementation of this operation is not robust."

I hesitated for the wontfix, which in the end was merely based on the supposition that the existing plugins were providing the requested feature in a satisfying way.

If this is not the case, one possible reason could be that the feature is much more "naturally" done in Trac itself (easier to implement in a more robust way). As I remember having coded that feature once as part of an experimental branch (comment:2, comment:6), this could well interest me again in the future, e.g. after or jointly with #31, eventually based on something like TracDev/Proposals/TracRelations.