.

Abc November 25, 2023

.

3 answers

1 vote
Joseph Chung Yin
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
November 25, 2023

@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/

https://support.atlassian.com/jira-service-management-cloud/docs/how-is-jql-used-to-create-sla-goals/

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

1 vote
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
November 25, 2023

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:

  • Remove the automatic assignment.  Issues should be queued up, or left in a backlog without assigning until people are able to pick them up.  Your teams should be looking at the backlog or queue when they are able to deal with new things, not having things forced on to them just because someone else wants it done now.
  • Ask why someone got the automatic assignment set up.  Keep asking "why" until you get an explanation rather than "that's the way we want to work"
  • Confront your managers.   "Confront" is an aggressive word in English, I originally wrote "Question your managers", but it sounds like you need to be a bit aggressive because you say "management is absent".  They clearly have no idea of what your team is doing or how it should be run.  That needs to be fixed, and it's not something you can do with the software.

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)

0 votes
Abc November 25, 2023

.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
TAGS
AUG Leaders

Atlassian Community Events