Computer systems don't always map directly to GTD concepts. I find that it helps me to think about how I would implement GTD on paper first and then see how something similar could be done with software.
In a paper system, when clarifying an inbox item, we decide the next action. If this one action isn't enough to achieve the goal, we decide on a project too. Then we organise, writing the action on the correct context list and the project on the Projects list.
When we are "Doing" with our paper system, we use context, time available, energy and priority to choose an action in the moment. We aren't encouraged to write down priorities since priorities shift too frequently. Instead, we are encouraged to rely on the intuitive feel for priorities that we gain from regular reviews. Once we have completed the next action for a project, we decide on another next action and write it on the correct context list.
Moving on to a computer system, we need it to support our workflow and store everything that we wrote down, but we don't need it to replace the thinking we did. Based on this reasoning, we don't need the computer system to track priorities because in GTD terms they relate to decisions made in the moment. All we really need is a project list and context lists.
One of the simplest GTD computer systems would be a document where the first page is the projects list and subsequent pages are the context lists. When evaluating a computer system, I have two main questions that I ask myself:
- Is it better than paper?
- Is it better than a simple document?
For me, the answer to both is usually 'no' for most computer systems. I think it is no accident that lots of people use things like Evernote and Obsidian for both their reference system and their list manager.
I am not sure what software you are using but it sounds like it might not be doing the basics very well. Could you tell us what you are using? Maybe someone else here uses the same software and can help you navigate its features.