A JIRA question that doesn’t belong in r/JIRA…

I recently started a position working with a team of developers that use JIRA. I have some software development experience, but mostly as an individual trying to automate things. There's more, but my goal isn't to bore you with my autobiography. In short, JIRA, SCRUM, and developing software as a team are pretty new to me. Also, my role is weird, but "product owner" is probably the closest thing.

I'm looking for guidance and frameworks that will help me learn about the software development process…from a team/project point of view. JIRA is advertised as a "project management tool", but I feel like it is missing something. This is difficult for me to describe without being too granular or getting into proprietary things. It's like trying to identify the unknown, unknown, lol.

I think what I'm looking for is a framework that covers the entire software development lifecycle, and all the things that happen outside of JIRA (e.g., requirements gathering, decision log, documentation, etc.). I understand that no two projects are the same, but I find it useful to have an "anchor" in my mind that acts as a place to start from. Use cases and specific examples are always helpful vs pure theory. I'm just looking for some references/links where I can read and educate myself. Thanks.