If we continue to use cherry-picks from master to maintenance branch to get tickets into the current release, we would benefit from a tool that visualizes which commits are in the maintenance branch and which commits are only on master but not in the maintenance branch. This can be done using the "git cherry" command-line tool, but the interface isn't that great. Our GUI could even have a button to generate the pull requests to perform the cherry-picks.
Alternatively, we could change our process to make commits directly on the maintenance branch and periodically merge maintenance into master. (This idea was opposed by ICU-TC.) This would eliminate the need to do manual accounting of which commits are on each branch.