Adding 'drop_open_issues' to StatusUpdate

Review Request #10075 — Created July 9, 2018 and submitted

Information

Review Board
master
9494233...

Reviewers

Adding 'drop_open_issues' to StatusUpdate.

This feature is needed by the Review Bot feature "Adding ability to drop old issues on new review." https://reviews.reviewboard.org/r/10061/.
The method finds all open issues associated with the status update's review (if it exists) and drops them. Smart enough to update the review request's timestamp and issues counts.

Unit tests!

Also, called the method (via the Review Bot changes) with a review request with previous status updates with open issues. Noticed the timestamp and issue count were correct, and old issues were dropped.

Description From Last Updated

This should also be done on release-3.0.x instead of master. Can you rebase?

daviddavid

E501 line too long (81 > 79 characters)

reviewbotreviewbot

We should import this from reviewboard.reviews.models.base_comment, to avoid potential circular import problems.

daviddavid

Please add this line back

daviddavid

There's an extra space after the """, and this should be written in the imperative rather than passive mood ("Drop …

daviddavid

I know a lot of old code doesn't have it, but can you add a module docstring here?

daviddavid

Can you specify that this is dropping open issues associated with a status update?

daviddavid

Same here.

daviddavid

Same here.

daviddavid

Same here.

daviddavid

Same here.

daviddavid

Same here.

daviddavid
jcannon
  1. I'll start on unit tests tomorrow.

    1. I didn't see any test files that test the StatusUpdate model (I see other ones for the Entry). (That makes sense because there wasn't much logic in StatusUpdate before).
      I plan on adding one, stop me if I'm way off track.

  2. 
      
jcannon
Review request changed

Change Summary:

Adding unit tests

Testing Done:

~  

Call the method (via the Review Bot changes) with a review request with previous status updates with open issues. Noticed the timestamp and issue count were correct, and old issues were dropped.

  ~

Unit tests!

  +
  +

Also, called the method (via the Review Bot changes) with a review request with previous status updates with open issues. Noticed the timestamp and issue count were correct, and old issues were dropped.

Commit:

-f842ea8e6475d07269280a0a320f5a070692513e
+b9e6631344294549686009178673b8a2c9799c5b

Diff:

Revision 2 (+168 -1)

Show changes

Checks run (1 failed, 1 succeeded)

flake8 failed.
JSHint passed.

flake8

jcannon
jcannon
  1. bump

  2. 
      
jcannon
  1. bump

  2. 
      
david
  1. 
      
  2. Show all issues

    We should import this from reviewboard.reviews.models.base_comment, to avoid potential circular import problems.

  3. Show all issues

    Please add this line back

  4. Show all issues

    There's an extra space after the """, and this should be written in the imperative rather than passive mood ("Drop open issues" instead of "Drops open issues")

  5. Show all issues

    I know a lot of old code doesn't have it, but can you add a module docstring here?

  6. Show all issues

    Can you specify that this is dropping open issues associated with a status update?

  7. Show all issues

    Same here.

  8. Show all issues

    Same here.

  9. Show all issues

    Same here.

  10. Show all issues

    Same here.

  11. Show all issues

    Same here.

  12. 
      
david
  1. 
      
  2. Show all issues

    This should also be done on release-3.0.x instead of master. Can you rebase?

  3. 
      
misery
  1. 
      
  2. any progress here? :-)

    1. My company is no longer planning on upgrading to ReviewBoard 3.0 for the forseeable future. Feel free to steal my code and continue the changes if you'd like.

  3. 
      
david
  1. Going to make some minor changes and get this landed. Thanks!

  2. 
      
jcannon
Review request changed

Status: Closed (submitted)

Change Summary:

Pushed to release-3.0.x (eb08b74)
Loading...