Custom Query (2152 matches)
Results (1066 - 1068 of 2152)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1113 | fixed | lists in extras serialized wrongly on get with the api. | kindly | kindly |
| Description |
Lists are being converted to unicode and then translated into a json when getting from the api. |
|||
| #1114 | fixed | CLI for viewing search index of a package | dread | dread |
| Description |
To see what lexemes are generated for debug purposes. |
|||
| #1115 | wontfix | can have two authzgroups with the same name | johnlawrenceaspden | |
| Description |
If you've got edit permission on an authzgroup, then you can change its name to be the same as another existing authzgroup. This causes some strange UI effects at worst, and probably causes worse problems somewhere else. Is there any reason why changing the names of existing authzgroups should be allowed? And if so, name collisions should presumably be guarded against in both the name-changing and creation functions |
|||
Note: See TracQuery
for help on using queries.
