@Abc -
As I agreed with what @Nic Brough -Adaptavist- suggested, one other key that you should also focus on is on the SLA associated with each issue. By utilizing on the SLA data, it will give you more insights on how issue management is conducted in your JSM project.
Here are a few reference links on JQL with SLA -
https://support.atlassian.com/jira-service-management-cloud/docs/write-jql-queries-for-slas/
More importantly, issue assignments along is just a part of the issues processing management process. In each project, SLA can be customized that truly reflects how your team is working when processing issues within a project.
Hope this also helps.
Best, Joseph
Welcome to the Atlassian Community!
Here, you have a people problem, not a software problem. You've configured the software to do a bad thing (automatically assigning things to people without any thought) because your team is broken.
You need to do three things here:
As for the JQL question, it's easy - you just need a clause that identifies your "stale" issues. How are you identifying them in Jira? What field are you looking at that says an issue is "stale"? (For example, a custom field being filled could do it, but in some places, I'd look to the updated date - if it's over a month old in a service desk project, then there's a good chance the problem has gone away, or wasn't really needed by the requestor because they've not chased it up)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.