Hide Forgot
Description of problem: when I try to clone plan there is no parent set. parent should be set up automatically when plan is cloned Version-Release number of selected component (if applicable): Nitrate 3.5.0 © 2011 Red Hat, Inc. All rights reserved. How reproducible: always Steps to Reproduce: 1. have tcms plan number = 1 2. make a clone of this plan 3. There should be parent=1 in the cloned plan. Actual results: no parent was set Expected results: parent = number of plan from you are cloning on it should be similar to bugzilla when you create clone bug and bugzilla set up depends on Additional info: any-tcms-plan[id=1] |______clone-of-any-tcms-plan[parent=1]
(In reply to comment #0) > Description of problem: > when I try to clone plan there is no parent set. parent should be set up > automatically when plan is cloned > > Version-Release number of selected component (if applicable): > Nitrate 3.5.0 © 2011 Red Hat, Inc. All rights reserved. > > How reproducible: > always > > Steps to Reproduce: > 1. have tcms plan number = 1 > 2. make a clone of this plan > 3. There should be parent=1 in the cloned plan. > > > Actual results: > no parent was set > > > Expected results: > parent = number of plan from you are cloning on > it should be similar to bugzilla when you create clone bug and bugzilla set up > depends on > > Additional info: > any-tcms-plan[id=1] > |______clone-of-any-tcms-plan[parent=1] your requirement is conflict with bug 722268, in that bug description, if plan1 has parent plan A, then clone new plan 2 from plan 1. the plan2's parent should auto be A. Which solution do you think is better ?
*** Bug 722268 has been marked as a duplicate of this bug. ***
(In reply to comment #1) > (In reply to comment #0) > > Description of problem: > > when I try to clone plan there is no parent set. parent should be set up > > automatically when plan is cloned > > > > Version-Release number of selected component (if applicable): > > Nitrate 3.5.0 © 2011 Red Hat, Inc. All rights reserved. > > > > How reproducible: > > always > > > > Steps to Reproduce: > > 1. have tcms plan number = 1 > > 2. make a clone of this plan > > 3. There should be parent=1 in the cloned plan. > > > > > > Actual results: > > no parent was set > > > > > > Expected results: > > parent = number of plan from you are cloning on > > it should be similar to bugzilla when you create clone bug and bugzilla set up > > depends on > > > > Additional info: > > any-tcms-plan[id=1] > > |______clone-of-any-tcms-plan[parent=1] > > your requirement is conflict with bug 722268, in that bug description, if plan1 > has parent plan A, then clone new plan 2 from plan 1. the plan2's parent should > auto be A. > Which solution do you think is better ? I meant the same thing in bug 722268. Solution which Petr described is OK also to me.
Hi How it looks with this bug? Because right now we are doing test plans and this thing can cause lost plans.
(In reply to comment #4) > Hi > How it looks with this bug? Because right now we are doing test plans and this > thing can cause lost plans. (In reply to comment #4) > Hi > How it looks with this bug? Because right now we are doing test plans and this > thing can cause lost plans. This bug will fix in tcms 3.6.z. parent's number of plan will default set to the id of the plan you clone from. Which solution do you think is better?
Hi. I think Petr solutions ok, so yes for you decription. So set the id of the plan which I'm cloning as a parent number. Like in bugzilla. For example I'm cloning plan 123. The new plan id is for example 456 and the parent bumber is 123. Tomas Pelka agreed with this solution in comment #3
The implementation goes rather easy for us to make this happen. My concern is if this is a common preference for most of TCMS users, so it is reasonable enough for us to add this.
commit da5c83512e32b5e023f6090daa7036dd5613baa7: parent's number of plan will default set to the id of the plan you clone from.
If there's a concern that this change won't be accepted by majority of TCMS users, then lets give them a choice: Add this to the https://tcms.engineering.redhat.com/plans/clone/ page: Set parent plan to: [ ] none [ ] custom: ____ [ ] cloned plan's parent [x] cloned plan itself
Verify 3.8.1 verify steps: 1. choose a test plan. 2. click the 'Clone Plan'btn. 3. fill some filed on clone plan page 4. click on save btn. Actional result: parent's number of plan will default set to the id of the plan you clone from. ====================================================== Hi Ales, this bug have been fixed and verified ,i 'll close this bug. so could u fill a new RFE bug with it. thanks, jinli (In reply to comment #9) > If there's a concern that this change won't be accepted by majority of TCMS > users, then lets give them a choice: > > Add this to the https://tcms.engineering.redhat.com/plans/clone/ page: > > Set parent plan to: > [ ] none > [ ] custom: ____ > [ ] cloned plan's parent > [x] cloned plan itself