Folijet - Jira cleanup and tech debt filters
**************************** UNDER CONSTRUCTION ******************************
Below is a table of cleanup filters that @Ann-Marie Breaux (Deactivated) uses to ensure the Folijet backlog is clean and comprehensive. These filters are run every few days and any new issues cleaned up..
Assumptions:
All UXPROD features assigned to the Folijet dev team are linked to an Epic, with
A "defines" link type
The Epic in the feature's Epic field (usually Batch importer, Inventory, or Enhanced consortia support)
All issues (stories, bugs, tasks, tech debt) assigned to the Folijet dev team have an Epic assigned to them (usually Batch importer, Inventory, or Enhanced consortia support)
All issues (stories, bugs, tasks, tech debt) assigned to the Folijet dev team have a Feature linked to them, using the "defines" link type
All issues (stories, bugs, tasks, tech debt) assigned to the Folijet dev team have a value in the Release field. The Release field value in these issues should match the Release value in the issue's associated Feature.
All issues (stories, bugs, tasks, tech debt) assigned to the Folijet dev team have a value in the Story points field, even if the value is 0. If there's no points, then the issue should have a label of "needs-points"
When in doubt about any of these values, check with the Folijet Product Owner and/or Scrum Master
After cleaning up the filter, re-search it to confirm all issues have been removed or cleaned up
Jira filter | Why is it used? | How are issues resolved? | Notes |
|---|---|---|---|
If a bug is not assigned to a dev team, it may not be noticed. | Look up the Jira project on FOLIO Module/JIRA project-Team-PO-Dev Lead responsibility matrix. Assign to the correct dev team. Add a comment to the Team PO and/or dev lead alerting them and asking them to reassign if not correct. |
| |
To identify FAT manual test issues and closed Karate test failure issues that do not have story points. |
|
| |
To identify closed Folijet issues missing story points. |
|
| |
To identify issues in Data Import projects and owned by Folijet, so that they can be added to the appropriate features | Confirm that the issue belongs to Folijet. Assign release value, if there is not one (even if the value is Not scheduled). If the issue belongs to a known flower release, look up the Folijet feature for that release, and assign the proper feature with link type of "defines". | If there's no feature, there also may not be a Release or an Epic. You can assign those while cleaning up in this filter, or wait and catch them in later filters. | |
To identify issues in Data Import projects without Folijet assigned, so that the correct dev team can be added. | Confirm that the issue belongs to Folijet. Assign Dev team = Folijet | Note that Spitfire works in the same projects as Folijet, so if questions, ask the Spitfire POs or on the folifire Slack channel. | |
To identify issues in Data Import projects and assigned to Folijet, but without an Epic assigned | Assign appropriate Epic (usually Batch importer, Inventory, or one of the ECS projects) |
| |
|
|
|
|
Bugs assigned to Folijet that the PO has not yet assigned a priority to | Assign the priority: 1: only if Data Import or Inventory is basically broken/unuseable 2: high priority; fix ASAP 3: regular priority: fix when possible 4: fix if nothing else to do |
| |
Bugs assigned to Folijet that have been closed, but do not have an RCA group | Assign the RCA group. If you cannot figure it out, ask the developer to assign it. |
| |
Issues that have been completed, but still have the folijet-refinement label | Remove the label |
| |
Issues in the Inventory modules that Folijet handles and are not linked to any Folijet feature | Assign a Folijet feature and use link type "defines" If the issue cannot be assigned to a feature in a flower release, consider https://folio-org.atlassian.net/browse/UXPROD-2334 (Misc unscheduled bugs) https://folio-org.atlassian.net/browse/UXPROD-4515 (Misc enhancements) | This only retrieves issues created after 1 Jan 2022, since Prokopovych owned Inventory before Folijet. If any issues belong to other Inventory modules and/or to Spitfire, do not edit them. Spitfire uses other rules for adding features. | |
Issues assigned to Folijet that do not have a value in the release field | If the issue is assigned to a feature, then note the release value in the feature, and assign the same to the issue If the issue is not assigned to a feature, then figure out which feature it should belong to first, link to the feature, and then assign the feature's release value to the issue |
| |
Issues assigned to Folijet dev team that do not have a feature link | Confirm the issue belongs to Folijet, and assign the proper feature link as "defines" Also check to see if the issue has an Epic assigned, and if not, then assign that as well | Issues for this filter may have been cleaned up in earlier filters | |
Issues assigned to Folijet dev team that do not have an Epic | Any Folijet issues features should have an Epic value in the top portion of the issue, just below the Release value. If there, is not one, assign one based on 1) the epic that the linked feature is assigned to, or 2) one of the following default epics:
|
| |
Issues that should either have points or be marked as needing points | Is this an issue that would be zero points (FAT manual test review, FAT Karate test failures that closed automatically)?
Is this an issue that developers have already worked on?
Is this a new issue that no one seems to have worked on?
|
| |
When issues are first created, the do not have points, but they will usually have the needs-points label. Once points are assigned (even if the points = 0), the label should be removed | Remove the needs-points label |
| |
When issues are first created, the do not have points, but they will usually have the folijet-refinement label. Once points are assigned (even if the points = 0), the label should be removed | Remove the folijet-refinement label | There also may be a needs-points and/or next-refinement label that should be removed | |
Mostly only bugs need RCA values | Skim through the list. If any stories (green) or tasks (blue), check to see if they are RRT. If not RRT, then change the RCA value to none, which will cause it to disappear from the UI | For any bugs with RCA value of not yet assigned, they can stay as-is, until the bug has been closed. | |
Issue closed as won't do, but no story points assigned | Add value of 0 for Story points | All closed Folijet Jira issues must have points, even if the value is 0 | |
Inventory issues that have not yet been reassigned from Prokpovych to Folijet or Spitfire | Not urgent, but at some point, these need to be reassigned to Folijet or Spitfire. Probably best to go through these with someone from Spitfire |
| |
To identify issues for a particular release that are missing a release value. These are identified by puling a list of all issues linked to the flower's Folijet features as "defines" links. | Scroll down through all the issues at the top of the list until you get to the current flower release. When done with those, reverse the sort order and scroll through all the issues at the end of the list until you get to the current flower release. If issue belongs in the release, assign the appropriate release value. If issue does not belong in the release, check the its feature link, and reassign to a different feature. See notes for some release types that are OK in the current release. Issues with the (next flower) release should never be in the (current flower) release | Note that this list returns all issues associated with a particular flower's features. Some will have different values from the regular flower release value. Some of these are OK.
| |
Issues has been closed, but still has label needs-testrail | Check to see if there is a linked TestRail. If yes, change needs-testrail to has-testrail If no, ask the QA to write and link TestRail(s) |
| |
Cleanup - (flower) Folijet remaining open/draft/blocked non-FAT issues | Issues that must be completed in the main flower release or the bugfix release. FATs are removed so that they don't mask the development and release issues | No need to review until close to the end of the flower development cycle. Then review closely. Once the (flower) Bugfix release value is available, some issues may change to that. Once the (flower) CSP release values are available, some issues may change to that, ALL the issues in this filter must be closed or moved by the end of the (flower) Bugfix release date. | If an issue moved to (flower) CSP release or a later flower release, then the feature link probably needs to be changed as well |
Issues that must be completed in the main flower release or the bugfix release, including the FATs | Make sure these are al closed by the end of the flower release |
| |
|
|
|
|
Add release note tech debt |
|
|
|
Add test rail tech debt |
|
|
|