Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Multi Assign Priority/Status in Test Plan Removes Values in Test Cases #1318

Closed
lefirenet opened this issue Jan 21, 2020 · 0 comments
Closed

Multi Assign Priority/Status in Test Plan Removes Values in Test Cases #1318

lefirenet opened this issue Jan 21, 2020 · 0 comments
Labels
bug high priority

Comments

@lefirenet
Copy link

Description of problem

When using the multi assign priority or status actions in test plan listing screen, all marked test cases' summary/title, text and notes are removed

Version or commit hash (if applicable)

7.3

Steps to Reproduce

  1. Create a Test Plan
  2. Create a couple of test cases (title and notes filled)
  3. Select Test Cases for editing by ticking their checkbox
  4. Set new priority or status
  5. Access the test cases

Actual results

The summary/title, test and notes in the test cases are gone.

Expected results

Only priority or status should've been updated

Additional info (Python traceback, logs, etc.)

Replicated on https://public.tenant.kiwitcms.org/
atodorov added a commit that referenced this issue Jan 21, 2020
@atodorov
Add test for #1318
b7ad27e 
this fails currently b/c TestCase.update API method clears
summary & text
atodorov added a commit that referenced this issue Jan 21, 2020
@atodorov
Fix TestCase.update() handling of unspecified fields. Fixes #1318
891fa39 
this still allows the API caller to specify only the fields which
they want to modify but properly initializes the rest of the values
based on the current object instance instead of reseting them
to None.
atodorov added a commit that referenced this issue Jan 21, 2020
@atodorov
Fix TestCase.update() handling of unspecified fields. Fixes #1318
9323178 
this still allows the API caller to specify only the fields which
they want to modify but properly initializes the rest of the values
based on the current object instance instead of reseting them
to None.
atodorov added a commit that referenced this issue Jan 21, 2020
@atodorov
Add test for #1318
4ceb419 
this fails currently b/c TestCase.update API method clears
summary & text
@atodorov atodorov mentioned this issue Jan 23, 2020
Closed
@atodorov atodorov mentioned this issue Feb 10, 2020
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug high priority
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@atodorov @lefirenet