"git branch" is probably the wrong tool for this job: it will only tell you about branches that still exist, and merged feature branches aren't something you particularly need lying around.
Its definition of "merged" also can't tell you "when" - it just means there's at least one path working backwards from "master" that gets you to the current tip of that branch. (A commit is never really "on" a branch in git; a branch only exists as a pointer to a single commit, and from there to its entire history.)
A different approach to the problem is this:
git log --first-parent master..develop
As long as the only commits that get into develop are merge commits - no fast-forward merges or direct commits to that branch - this will give you a list of them.
- The
--first-parent
stops it listing out the individual commits from each feature merged in.
- The
master..develop
notation means roughly "everything on develop that's not also on master". (Again, "on" actually means "reachable from the current tip of".)
You can use the --pretty
option to customise exactly what gets shown here. I frequently use it with --pretty='format:%s'
which just shows the commit message on the merge commit.