Description:

Customer Explanation:

For shared AAP instances which serve 100s of customers - We need to improve prioritization capabilities for AAP Jobs. At the moments, its FIFO based. An important remediation job could be stuck in the queue for hours while longer running “scan” jobs occupy Tower forks capacity.

Hence, we would like to request a feature for providing a priority number could be any number - say 0 to 1000 that can be used to assign the relative priority at Job Templates, Projects (should then apply to all Templates defined from that Project) and Organization level (should then apply to all jobs run for a particular Org). 

Priority sequence can be like:

1. Org
2. Project
3. Job Template

If 2 Orgs have the same Priority, then the priority is determined by the other 2 priorities defined at Project or Template level

SLAs getting impacted for important patching playbooks/jobs waiting for other jobs in the queue.