Stack Exchange network consists of 183 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.
Unfortunately following those instructions will not not enable you to fix the OP's problem. I tried it and it doesn't work - priority does not seem to be available in that view.
I don't consider myself an agile purist but I do think the distinctions between Kanban and Scrum are important. Timeboxing in Scrum is probably the biggest one (and is important for predictability and forward planning). Just to make things more confusing you could look at Scrumban (leansoftwareengineering.com/ksse/scrum-ban). That's basically what I use at the moment.
Take a look at Tempo (tempoplugin.com). It's not really a Gantt chart tool as such but I think it's more compatible with agile and the particular problem you're trying to solve.
This is good stuff. I'd caveat that relying too heavily on certifications can be dangerous (it's not actually that difficult to get certified - much more difficult to do this stuff in practice) so you definitely need to dig in to the detail further at the interview stage.
I don't agree with the idea that 'you aren't that important to your team if they aren't reporting to you'. PMs regularly lead teams that they do not manage and the best ones are often popular and successful because they actively champion, defend and support their project team regardless of this.
