Tasks #12002
closedMake custom query for Pending Backport tickets with empty backport field
0%
Description
This is another way that backport tasks "fall through the cracks" - since the Backport field is not filled in, the issues do not show up in our custom queries, even though they are marked Pending backport.
Currently there are quite a number of these: http://tracker.ceph.com/projects/ceph/issues?utf8=%E2%9C%93&set_filter=1&f[]=status_id&op[status_id]=%3D&v[status_id][]=14&f[]=cf_2&op[cf_2]=!*&f[]=&c[]=project&c[]=tracker&c[]=status&c[]=priority&c[]=subject&c[]=assigned_to&c[]=updated_on&c[]=category&c[]=fixed_version&c[]=cf_3&group_by=
Please consider making this into a custom query and updating [[HOWTO_triage_incoming_Pending_backport_issues]].
I guess such tickets don't happen very often, so I suppose checking for them once a month or even bimonthly would be enough.
Updated by Loïc Dachary almost 9 years ago
Ouch, nice catch ! Making a public custom query is going to make it visible everywhere and maybe confuse people ?
Updated by Loïc Dachary almost 9 years ago
- Status changed from New to In Progress
Updated by Loïc Dachary almost 9 years ago
- Project changed from Stable releases to devops
The devops project is not ideal for improvements related to the stable releases maintenance. It would be nice that the stable releases project only contains backport tracking and no issues related to the maintenance of the process. I'm not convinced it's a good thing. Maybe I'm wrong. What do you say ?
Updated by Nathan Cutler almost 9 years ago
- Status changed from In Progress to Resolved
@dachary - All good from my side.