Move BugTracker into reviewboard.hostingsvcs.base.

Review Request #14586 — Created Sept. 4, 2025 and updated

Information

Review Board
release-7.1.x

Reviewers

The rest of our base classes have all been moved into the
reviewboard.hostingsvcs.base module, but the bug tracker interface was
still in the top-level directory. This change moves it and updates
the services which use it to use the new import.

Ran unit tests.

Summary ID
Move BugTracker into reviewboard.hostingsvcs.base.
The rest of our base classes have all been moved into the `reviewboard.hostingsvcs.base` module, but the bug tracker interface was still in the top-level directory. This change moves it and updates the services which use it to use the new import. Testing Done: Ran unit tests.
towzyqzmzvrqryzottmxpryxqrnznnzl
Description From Last Updated

Can we name this BaseBugTracker?

chipx86chipx86

This needs version information stating it moved.

chipx86chipx86

Missing the Instance Variables block and a comment.

chipx86chipx86

We can probably say a BugInfo dictionary (linking to the class).

chipx86chipx86

I know this is old code, but this comment feels a bit out of place these days. Maybe worth a …

chipx86chipx86

We should switch to the new pathed keys in Djblets, since there's user input (bug IDs) in here.

chipx86chipx86

TYPE_CHECKING sorts first.

chipx86chipx86

Do we want to make this a Literal[...]?

chipx86chipx86
chipx86
  1. 
      
  2. Show all issues

    Can we name this BaseBugTracker?

  3. Show all issues

    This needs version information stating it moved.

  4. Show all issues

    Missing the Instance Variables block and a comment.

  5. reviewboard/hostingsvcs/base/bug_tracker.py (Diff revision 1)
     
     
     
    Show all issues

    We can probably say a BugInfo dictionary (linking to the class).

  6. Show all issues

    I know this is old code, but this comment feels a bit out of place these days. Maybe worth a revisit.

  7. Show all issues

    We should switch to the new pathed keys in Djblets, since there's user input (bug IDs) in here.

  8. 
      
david
david
david
maubin
  1. Ship It!
  2. 
      
chipx86
  1. 
      
  2. Show all issues

    TYPE_CHECKING sorts first.

  3. reviewboard/hostingsvcs/base/bug_tracker.py (Diff revision 4)
     
     
     
    Show all issues

    Do we want to make this a Literal[...]?

  4. 
      
david
Review request changed
Commits:
Summary ID
Move BugTracker into reviewboard.hostingsvcs.base.
The rest of our base classes have all been moved into the `reviewboard.hostingsvcs.base` module, but the bug tracker interface was still in the top-level directory. This change moves it and updates the services which use it to use the new import. Testing Done: Ran unit tests.
towzyqzmzvrqryzottmxpryxqrnznnzl
Move BugTracker into reviewboard.hostingsvcs.base.
The rest of our base classes have all been moved into the `reviewboard.hostingsvcs.base` module, but the bug tracker interface was still in the top-level directory. This change moves it and updates the services which use it to use the new import. Testing Done: Ran unit tests.
towzyqzmzvrqryzottmxpryxqrnznnzl

Checks run (2 succeeded)

flake8 passed.
JSHint passed.