1
Select a Branch and enter the branch divergence base tag in Base Tag. Use the dropdown button to quickly select recent tags.
2
Select modules to query in Modules. Check ALL for all modules, or uncheck and Ctrl+click to select individual modules.
3
Click Generate Patch List to query commits added to master after the base tag. Commits already cherry-picked to the branch are auto-detected and shown with a Merged badge.
4
Record one of Merge (planned cherry-pick) / Keep (on hold) / No Need (unnecessary) for each commit. Saved to DB immediately on click; click the same button again to cancel the decision.
5
If a Jira ticket is linked to a commit, Automated Test and Customer Notify info is shown. Green background means Notify: YES, red background means not entered.
6
Results are cached. If new commits are added to master, the latest data is fetched automatically on the next query. Commits recorded as Keep remain in the list even if they fall outside the base_tag range.
7
The Merged badge appears in two colors. Blue means the commit was detected on the branch via patch-id (exact match). Amber means the same Jira ticket was found on the branch but the diff content differs — typically a cherry-pick resolved with conflicts. Revert commits are excluded from Jira matching.
8
Click the icon on the right of each commit to add a comment. Once saved, the icon turns purple . Click the icon again or the comment text to edit. Comments are saved per commit per branch.