Re: [Django] #31597: New "Clear all filters" shown always in raw_id_fields popup

#31597: New "Clear all filters" shown always in raw_id_fields popup ---+-- Reporter: frnhr |Owner: nobody Type: Uncategorized | Status: new Component:

Re: [Django] #31596: ForeignKey.validate() should validate using the base manager.

#31596: ForeignKey.validate() should validate using the base manager. --+-- Reporter: Jon Dufresne |Owner: nobody Type: Bug | Status: new Component: Forms

[Django] #31597: New "Clear all filters" shown always in raw_id_fields popup

#31597: New "Clear all filters" shown always in raw_id_fields popup -+ Reporter: frnhr | Owner: nobody Type: Uncategorized | Status: new Component:

Re: [Django] #31597: New "Clear all filters" shown always in raw_id_fields popup

#31597: New "Clear all filters" shown always in raw_id_fields popup ---+-- Reporter: frnhr |Owner: nobody Type: Uncategorized | Status: new Component:

Re: [Django] #12203: ManyToManyField with through model can't be used in admin

#12203: ManyToManyField with through model can't be used in admin -+- Reporter: David Gouldin|Owner: nobody Type: Bug | Status: new

[Django] #31596: ForeignKey.validate() should validate using the base manager.

#31596: ForeignKey.validate() should validate using the base manager. + Reporter: Jon Dufresne | Owner: nobody Type: Bug | Status: new Component: Forms

Re: [Django] #31597: New "Clear all filters" shown always in raw_id_fields popup

#31597: New "Clear all filters" shown always in raw_id_fields popup ---+-- Reporter: frnhr |Owner: frnhr Type: Uncategorized | Status: assigned Component:

Re: [Django] #31597: New "Clear all filters" shown always in raw_id_fields popup

#31597: New "Clear all filters" shown always in raw_id_fields popup ---+-- Reporter: frnhr |Owner: nobody Type: Uncategorized | Status: new Component:

Re: [Django] #31595: models.Datefield being localized where it shouldn't

#31595: models.Datefield being localized where it shouldn't -+- Reporter: akshaysalunke13 |Owner: nobody Type: Bug | Status: new Component:

Re: [Django] #31595: models.Datefield being localized where it shouldn't

#31595: models.Datefield being localized where it shouldn't -+- Reporter: akshaysalunke13 |Owner: nobody Type: Bug | Status: new Component:

Re: [Django] #11157: slugify and admin javascript URLify function produce different strings

#11157: slugify and admin javascript URLify function produce different strings --+ Reporter: keeperofkeys |Owner: nobody Type: Cleanup/optimization | Status:

Re: [Django] #11157: slugify and admin javascript URLify function produce different strings

#11157: slugify and admin javascript URLify function produce different strings -+- Reporter: keeperofkeys |Owner: Andy Type: | Chosak Cleanup/optimization

Re: [Django] #31595: models.Datefield being localized where it shouldn't

#31595: models.Datefield being localized where it shouldn't -+- Reporter: akshaysalunke13 |Owner: nobody Type: Bug | Status: new Component:

[Django] #31595: models.Datefield being localized where it shouldn't

#31595: models.Datefield being localized where it shouldn't -+- Reporter: | Owner: nobody akshaysalunke13| Type: Bug| Status: new

Re: [Django] #31595: models.Datefield being localized where it shouldn't

#31595: models.Datefield being localized where it shouldn't -+- Reporter: akshaysalunke13 |Owner: nobody Type: Bug | Status: new Component:

Re: [Django] #31595: models.Datefield being localized where it shouldn't

#31595: models.Datefield being localized where it shouldn't -+- Reporter: Akshay Salunke |Owner: nobody Type: Bug | Status: closed Component: