• 
  
    
 
    
 
    

    



    
    
    
    
     
    




    
 
    

  
    



    
 

 

  

  

 

    


  
    





    
 
    



  

    
 
 
    
  
    Name built-in hosting service bug trackers after their product.
    
 
    

    



 
    
 
    

  Review Request #15350
  —
  Created Sept. 28, 2026 and updated 

 
    


    




    




    






 
    
  
    
   Information

  
    



    
 
 
    
  david
 
    

    





    
 
 
    
  Review Board
 
    

    





    
 
 
    
  release-9.x
 
    

    





    
 
 
    
  
 
    

    





    
 
 
    
  
 
    

    



 
    



 
    
  
    
   Reviewers

  
    



    
 
 
    
  reviewboard
 
    

    





    
 
 
    
  
 
    

    



 
    



    


    
 
    




  

    
 
 
    
  
    This change adds a new helper to BaseHostingService that returns the
    
display name of a service's built-in bug tracker. It uses the service's
    
bug_tracker_label when the service sets one (for example, "GitHub
    
Issues"). Otherwise, it falls back to a generic name based on the
    
service.
    

    While in here, I've made it so GitLab now sets bug_tracker_label to
    
"GitLab Issues". GitLab doesn't yet implement the bug tracker backends,
    
but I didn't want to forget this while I was thinking about names.
    

    Built-in trackers materialized from legacy settings now use this name
    
as-is, without the repository name added. The name is the field label
    
on review requests, so "GitHub Issues" reads better than "GitHub
    
(myrepo)".
    
 
    

    





  

    
 
 
    
  
    Ran unit tests.
    
 
    

    




 
    

    





    
 
    




  
    
 
 
    
  


    
 
    
  
   
    

    Summary
    ID

   
    
      
  

   
    

    

     
    
      Name built-in hosting service bug trackers after their product.
      
    This change adds a new helper to `BaseHostingService` that returns the
display name of a service's built-in bug tracker. It uses the service's
`bug_tracker_label` when the service sets one (for example, "GitHub
Issues"). Otherwise, it falls back to a generic name based on the
service.

While in here, I've made it so GitLab now sets `bug_tracker_label` to
"GitLab Issues". GitLab doesn't yet implement the bug tracker backends,
but I didn't want to forget this while I was thinking about names.

Built-in trackers materialized from legacy settings now use this name
as-is, without the repository name added. The name is the field label
on review requests, so "GitHub Issues" reads better than "GitHub
(myrepo)".

Testing Done:
Ran unit tests.
    
     
    

        		
    lmxpuqwnlqlwkxupxqpoxvxkyktpqqnk

   
    


      
 
    

    
    
 
    

    






 









 
    

    



  
    
 
    

    


    












    
 




 
    
  
    

   
    

   
    

    
    

Checks run (2 succeeded)

    
    
    
    
     


      


     
    
    
   
    


  
    
  
    
  
    


    

 
    
 flake8
 passed.
 


    


 
    
 JSHint
 passed.