Feature #4403
closed
Copy with related task
Added by Alain V. over 14 years ago. Updated almost 11 years ago.
0%
Description
In our way of working in our company, when we get a ticket on our software from the customer that we consider as bug, we copy it to the validation project for debugging.
The option copy of a task is nice for that, but would it be possible to create also automatically the related task.
So for us for a bug in our validation project we would know this one comes from a customer and not from our validation process.
Thank you
Files
| implement_custom_copies.patch (6.08 KB) implement_custom_copies.patch | implementation of custom copies (missing creation UI) | James Bernard, 2009-12-21 02:57 | |
| 0100-adstec-copy_and_relate.patch (2.09 KB) 0100-adstec-copy_and_relate.patch | patch copy and relate | Karl-Heinz Nirschl, 2010-05-05 14:44 | |
| copy_to_another_project_and_relate.patch (1.75 KB) copy_to_another_project_and_relate.patch | Paul Preece, 2010-06-07 13:28 | ||
| ro4403-copy_improvements.patch (5.18 KB) ro4403-copy_improvements.patch | Patch created against trunk @ r7630. | Mischa The Evil, 2011-10-20 22:26 | |
| ro4403-copy_improvements.jpg (31.6 KB) ro4403-copy_improvements.jpg | Screenshot of the patched feature. | Mischa The Evil, 2011-10-20 22:26 |
Related issues
Updated by Jean-Philippe Lang over 14 years ago
Do you mean automatically adding a relation between the original issue and the copied issue, so that the copied issue is related to the original issue?
Updated by Alain V. over 14 years ago
Jean-Philippe Lang wrote:
Do you mean automatically adding a relation between the original issue and the copied issue, so that the copied issue is related to the original issue?
Exactly Jean-Philippe!
but not necessary automatically. Maybe be optionnal in the copy window or configurable.
Updated by Mischa The Evil over 14 years ago
Alain V. wrote:
Jean-Philippe Lang wrote:
Do you mean automatically adding a relation between the original issue and the copied issue, so that the copied issue is related to the original issue?
Exactly Jean-Philippe!
but not necessary automatically. Maybe be optionnal in the copy window or configurable.
+1 on such a feature. But I personally think that it's best to make it indeed optional through e.g. a checkbox on the issue copy-view. Maybe a new issue-relation type would be best too? One like "Copied" or "Branched"? Any thoughts?
Updated by James Bernard over 14 years ago
I wrote a patch that addresses that request
This patch implements what I call "custom copies" which are standard copies but with all settings automatically set, so that only one click is needed. "Related to" relation is also automatically set between the copied issue and its copy.
A custom copy defines a source issue by its project/tracker/status and the target issue by its project/tracker/status. In addition, it is possible to define a new status for the source issue once the copy is done.
Custom copies also have a label. When an issue is shown, only custom copies whose source issue criteria is matching the shown issue are displayed in the issue toolbar, beside usual Update/Move/Copy/Delete links.
Example: a custom copy labelled "confirm as bug" defining automatic copy from Hotline/Hotline/New to Validation/Bugs/New, with automatic change of Hotline/Hotline/New to Hotline/Hotline/Confirmed as bug after the copy.
Note: The patch does not include a form for creating custom copies. As of now, I'm creating them through SQL command...
Moreover I'm really a newbie in Ruby/Rails/Redmine world so the code is probably quite poor/wrong in some areas, I'm just providing the patch as an example of design...
Updated by Bill Tihen over 14 years ago
This patch seems VERY useful. We have over 200 users who submit tickets -- it would be GREAT if we had a "ME TOO" feature! That then created a related task (but not the regular relationship) -- we already use the regular relationship for related, but different tasks.
Also if a different relationship (a copied from or a "me too" relationship is available -- then that could be optionally extended so that we could manage one request and have all tasks reflect the changes made to the master task.
Updated by Alain V. over 14 years ago
Bill Tihen wrote:
This patch seems VERY useful. We have over 200 users who submit tickets -- it would be GREAT if we had a "ME TOO" feature! That then created a related task (but not the regular relationship) -- we already use the regular relationship for related, but different tasks.
Also if a different relationship (a copied from or a "me too" relationship is available -- then that could be optionally extended so that we could manage one request and have all tasks reflect the changes made to the master task.
A ME TOO is not like a vote?
Like me too i would like this feature?
Updated by Alain V. over 14 years ago
JP, it is not possible to put this in the version 1.0? I think this would help a lot of people. :o)
Updated by Karl-Heinz Nirschl almost 14 years ago
Hi,
i did an other patch, which just extends the copy and move dialog so that one could add a relation in one step. this is done for 0.9.3.
let me know if i should improve the code so it could be pushed to 1.0.
Updated by Paul Preece almost 14 years ago
Here's another patch with test against trunk.
We would certainly find this useful in a release.
Updated by Pedro Gutierrez almost 14 years ago
+1
I hadn't found this feature request and had, so, opened a similar one #5497
Updated by
Updated by Etienne Massip over 12 years ago
- Target version set to Candidate for next major release
Updated by Mischa The Evil over 12 years ago
- File ro4403-copy_improvements.patch ro4403-copy_improvements.patch added
- File ro4403-copy_improvements.jpg ro4403-copy_improvements.jpg added
I've extracted the relationship addition on copy > new from Brian Lindahl's patch in #7447, rebased it to source:/trunk@7630 and added two new relationtypes (copied to / copied from) to support the issue-copy relationship completely.
Any feedback is appreciated...
Updated by
Updated by Michael Jurisch about 11 years ago
Thanks a lot for that feature, but unfortunately defining the relation just work for tickets, that are copied within the same project, but I would need setting the relationship between a ticket in project A and its copied counterpart in project B.
Thanks in advance!
Updated by Mischa The Evil about 11 years ago
Michael Jurisch wrote:
[...] but unfortunately defining the relation just work for tickets, that are copied within the same project, but I would need setting the relationship between a ticket in project A and its copied counterpart in project B.
Shouldn't this be already possible by setting "Allow cross-project issue relations" to true combined with the implementation in r10491 for #6899 (2.2.0)?
Edit: in fact, it looks like this whole issue has been superseded by #6899. Could someone test this feature in recent Redmine version?
Updated by Mischa The Evil about 11 years ago
- Due date set to 2013-04-17
- Status changed from New to Needs feedback
Updated by Michael Jurisch about 11 years ago
Hey, Mischa, thanks a lot for that hint! I completely missed that option. :-( I am sorry!
This works perfect in Redmine 2.2.3.stable! Thanks!
Updated by Daniel Felix almost 11 years ago
- Status changed from Needs feedback to Closed
This one could be closed as there is user Feedback in note 18.
Thanks for your feedback.
Updated by Toshi MARUYAMA almost 11 years ago
- Target version deleted (
Candidate for next major release)