Bug 688495

hi Marian,

Please see this bug: https://bugzilla.redhat.com/show_bug.cgi?id=671507

In your case, its because cases 40139, 40140 are already inside plan 3438,
(see https://tcms.engineering.redhat.com/case/40139/?from_plan=3438, https://tcms.engineering.redhat.com/case/40140/?from_plan=3438).
So when you search cases, the result list will exclude them by default, we exclude them to ensure no duplicates.

As for the search dialog design, we're trying to enhance it.

Any problems, please feel free to reply, thanks.

(In reply to comment #1)
> hi Marian,
> 
> Please see this bug: https://bugzilla.redhat.com/show_bug.cgi?id=671507
> 
> In your case, its because cases 40139, 40140 are already inside plan 3438,

No, it isn't because of that. They weren't there. I added them from test case detail view right after reporting this bug. You can't evaluate this bug based on current state.

To reproduce this:

1. Go to https://tcms.engineering.redhat.com/plan/3438/#testcases
2. Click 'Add cases from other plans'
3. Filter by plan 989
4. Choose case 'xen / default' which is part of 989: https://tcms.engineering.redhat.com/case/8323/?from_plan=989

hi Marian,

Thanks for your concern on this, I've figured out why:

For https://tcms.engineering.redhat.com/case/8323/?from_plan=989, we could see
the case's related product is: Red Hat Enterprise Linux 5

Following your steps:
1. Go to https://tcms.engineering.redhat.com/plan/3438/#testcases
2. Click 'Add cases from other plans'

Note that in the case filter form, you could see the 'product' field is set to 'Red Hat Enterprise Linux 6' by default, this is because it's from plan 3438, it's relating product is rhel6.

For step 3, if you want to filter out the 'xen / default', you could either leave the product field blank(REHL6 by default), or select 'Red Hat Enterprise Linux 5'

Please have a try.

(In reply to comment #4)
> hi Marian,
> 
> Thanks for your concern on this, I've figured out why:
> 
> For https://tcms.engineering.redhat.com/case/8323/?from_plan=989, we could see
> the case's related product is: Red Hat Enterprise Linux 5
> 
> Following your steps:
> 1. Go to https://tcms.engineering.redhat.com/plan/3438/#testcases
> 2. Click 'Add cases from other plans'
> 
> Note that in the case filter form, you could see the 'product' field is set to
> 'Red Hat Enterprise Linux 6' by default, this is because it's from plan 3438,
> it's relating product is rhel6.
> 
> For step 3, if you want to filter out the 'xen / default', you could either
> leave the product field blank(REHL6 by default), or select 'Red Hat Enterprise
> Linux 5'
> 
> Please have a try.

Too much complicated (too many clicks required for most common action). It requires fix to follow user's workflow and expections.

> Too much complicated (too many clicks required for most common action). It
> requires fix to follow user's workflow and expections.

I think so too. It's complicated, It also took me 30 mins to figure out why.

@june, any ideas of improvements?

Created attachment 486188 [details]
Add cases from other plan

(In reply to comment #6)
> > Too much complicated (too many clicks required for most common action). It
> > requires fix to follow user's workflow and expections.
> 
> I think so too. It's complicated, It also took me 30 mins to figure out why.
> 
> @june, any ideas of improvements?

In the "Add cases from other plan", we set the product same as the prior plan by default. So you meet this problem, because you want to add other product cases.
From that should we set product blank by default? 

And to be simple the workflow, I have an other solution:  When click "Add Case from other plan", we list the simple query, case/plan keywords, let user to find which cases he want to add prior plan like the attachment. Please have a look see. How about it?

Thanks
June

(In reply to comment #7)
> In the "Add cases from other plan", we set the product same as the prior plan
> by default. So you meet this problem, because you want to add other product
> cases.
> From that should we set product blank by default? 

I vote for this. At least from point of view of my team this perfectly fits our typical use case. Of course, also opinion of other users matters. :)

> And to be simple the workflow, I have an other solution:  When click "Add Case
> from other plan", we list the simple query, case/plan keywords, let user to
> find which cases he want to add prior plan like the attachment. Please have a
> look see. How about it?

This sounds interesting, however I am not sure if I understand this proposal well.
The common action we are using is "add all/or some cases from particular plan". On the other hand addition of concrete case (without relation to some older plan) seems to be quite rare in our team (however it happens), so this is not so important as previous workflow, which is used really often. Does this proposal fit such use case?

TCMS 3.6 have been in maintenance phase, only urgent and that affect functionality to be fixed in this phase.
other bugs will be considered into 4.0's design.

So we will close this bug in this version.