The ls-ubuntu-tag-json code is actually for a different report. The reports rls-** reports are generated by "scripts/collect-bug-data" which is passed a json file with search criteria. That criteria follows:
Adding in 'champagne' as an additional filter to the search isn't a trivial matter because we want to search for bugs that are tagged 'rls-ff-incoming' and not '-rls-ff-notfixing' so we are using an and search in Launchpad. That being said if a bug is tagged 'rls-ff-incoming' and 'rls-ff-notifixing' I think something has failed in the rls bug process as when you tag it notfixing you should remove the incoming tag. So I'm just gonna modify the search to include champagne.
The ls-ubuntu-tag-json code is actually for a different report. The reports rls-** reports are generated by "scripts/ collect- bug-data" which is passed a json file with search criteria. That criteria follows:
"search_ criteria" : [
"distribut ion": "ubuntu",
"series" : [
"focal" ,
"NONE"
"status" : [
"New" ,
"Confirmed" ,
"Triaged" ,
"Incomplete" ,
"Incomplete (with response)",
"Incomplete (without response)",
"Fix Committed"
"rls- ff-incoming" ,
"-rls- ff-notfixing"
"tags_ combinator" : "All"
{
],
"In Progress",
],
"tags": [
],
}
],
Adding in 'champagne' as an additional filter to the search isn't a trivial matter because we want to search for bugs that are tagged 'rls-ff-incoming' and not '-rls-ff-notfixing' so we are using an and search in Launchpad. That being said if a bug is tagged 'rls-ff-incoming' and 'rls-ff-notifixing' I think something has failed in the rls bug process as when you tag it notfixing you should remove the incoming tag. So I'm just gonna modify the search to include champagne.