nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Query for "shame reports" - Issues assigned to me recently that I haven't responded to.

Allie Stewart

Hi,

I'm working on a filter for "shame reports" as it were. The logic is like this:

Issues assigned to me in the last 72 hours where I have not viewed or updated it them as of now.

I have this so far but I'm stuck with the updatedby part:

assignee = currentUser() and assignee changed to currentUser() after -3d and issuekey IN updatedBy("currentUser()") and updated <= -3d

I don't think the updatedby() function will take a variable. It seems to only take an actual user name. Which means that I can't use assignee either. So I'm not sure how to delimit this to updates made by me. I don't care if the issue was assigned to me and updated by someone else. I need to know where issues are assigned to me and waiting for my input, that I haven't given yet.

Thanks in advance for your help.

Accepted answers

Uday Kiran Bhaviri_cp1r58

You can try defining SLA as per your requirement in your JSM project.

Like first response should be less than 72 hours

https://support.atlassian.com/jira-service-management-cloud/docs/create-service-level-agreements-slas/

And then you can use this SLA in your JQL query

https://support.atlassian.com/jira-service-management-cloud/docs/write-jql-queries-for-slas/

All comments

Jack Brickey

Hi @Allie Stewart , I see you are using currentuser(). Are you doing this so that the filter can be shared? If not can you not simply use your username?

Danut M _StonikByte_

Hi @Allie Stewart,

Why not simply removing that condition. I think it makes no difference anyway.

assignee = currentUser() and assignee changed to currentUser() after -3d and updated <= -3d

Danut.

Uday Kiran Bhaviri_cp1r58

You can try defining SLA as per your requirement in your JSM project.

Like first response should be less than 72 hours

https://support.atlassian.com/jira-service-management-cloud/docs/create-service-level-agreements-slas/

And then you can use this SLA in your JQL query

https://support.atlassian.com/jira-service-management-cloud/docs/write-jql-queries-for-slas/

Allie Stewart

Yes, this is so it can be shared. I want them send the filter out daily to anyone.

Allie Stewart

Because I suppose it is possible for this to be assigned to Joe, and I need Joe's input, but then Sally updates the issue with something unrelated. But I still need Joe's input.

Perhaps that's not really an issue.

What I really need to know is issues that are waiting for Joe to respond and he hasn't. Basically a report that shows "these issues are waiting on you".

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management