Just wondering if this was a known bug? When changing ownership of a filter, the filter project ID's become numbers.
project in (OSRCORP, OSRCRD, OSREID, OSRMFT, OSRGMD, OSROMNI, OSROOTCS, OSROTHER, OSRPIX, OSRQCA, OSRQCES, OSRQCL, OSRQCT, OSRQED, OSRQES, OSRQGOV, OSRQIP, OSRQIS, OSRQL, OSRQMT, OSRQRS, OSRQTIL, OSRQTL, OSRQUEST, OSRQUIC, OSRSNAP, OSRMTRAIN, OSRFIRE) AND issuetype in ("Advice & Counsel", "Code Review", "Non-QC Inquiry", "OS Contributions") AND status != Closed
Filter after ownership change:
project in (10701, 10700, 10715, 10720, 10805, 10704, 10716, 10705, 10723, 10722, 10706, 10717, 10714, 10718, 10710, 10801, 10711, 10712, 10713, 10804, 10702, 13801, 10724, 10719, 10721, 10707, 11001, 13500) AND issuetype in ("Advice & Counsel", "Code Review", "Non-QC Inquiry", "OS Contributions") AND status != Closed
I have seen this happen with filters where ownership has changed, but have also seen it happen when that is not the case. Has anyone submitted a bug to Atlassian?
Here is a related topic:
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs