There's no way to do this well. You'd need a rank field (a simple numbering scheme will not work, you need a field built for actual ranking), but those only work for issues, and only really when the people doing the ranking can see all the issues, not just theirs. And certainly not for requests by organisation.
Best you can do is maybe ask the customers for some form of data that will help do some broad rankings - a good starter might be asking for size (number of people affected? How much it's costing?) and some form of rating of how bad it is (cosmetic, inconvenient for those affected, needing major hard work to work around, it's broken and can't be fixed) - those can be used to generate some form of rule for ranking broadly, and you could automate that calculation.
Thank you, Nic for taking your time to reply so quickly. The ranking is an important part of me with multiple clients. I have many duplicate ranking for tickets not knowing which ticket to be assigned to the developer for the respective customer. I will try as you suggested. Once again, thank you, much appreciated.
For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events