Hi Nadeem,
In such situation, we need to ensure that the new authorization object is imported first by development (or any other team who has created it) to all the DEV and Q systems to that this issue can not occur while importing the role.
Otherwise, if auto-import is not enable for TRs then you can import the transport request selectively to those system which has that authorization object.
Hope this helps
Thanks