Recent searches
No recent searches

James Harris
Joined Dec 06, 2021
·
Last activity May 17, 2022
Following
0
Followers
0
Total activity
6
Votes
2
Subscriptions
2
ACTIVITY OVERVIEW
BADGES
ARTICLES
POSTS
COMMUNITY COMMENTS
ARTICLE COMMENTS
ACTIVITY OVERVIEW
Latest activity by James Harris
James Harris commented,
Hi there,
I don't think there's necessarily an answer to this with the current functionality within views but here's my issue.
I have traditionally split out the 'Pending - All Tickets' view into two 'work' reports. The first of those is filtered by:
Status is Pending
Hours since update is greater than 168
This means any tickets that have been sat in pending for a week pop into this report for my team to follow up and nudge the requester, or move the ticket towards closure if the user does not engage.
That's all well and good but we've now introduced an additional element of complexity by 'switching on' the priority field. I now want to add conditions to the view which will show low priority tickets after 168 hours but high priority tickets after just 24 hours. In other words, I want to achieve:
IF Status is Pending
AND
((Priority = High
AND
Hours Since Update > 24)
OR
(Priority = Low
AND
Hours Since Update > 168))
THEN
Add the ticket the view
Is there anyway I can achieve this easily? I can set up separate views but I'm keen to keep the number of views we ask the team to monitor daily to a minimum.
Thanks!
View comment · Edited May 09, 2022 · James Harris
0
Followers
0
Votes
0
Comments
James Harris commented,
I'm after the same functionality as Nicole I think but struggling.
This is my table with values:
I want to display the percentage totals of those values against each row. So if we take December, we can see we have 51 + 66 tickets in total (117). I want display the two numbers as percentage totals of 117. When I set the Result Path Calculation to '% of Total' and 'On Rows', Explore calculates each entry as a percentage against the total number of results in my entire query, leaving me with this (which tells me nothing):
It's driving me round the bend but I'm sure I'm missing something really obvious!
View comment · Posted Dec 06, 2021 · James Harris
0
Followers
0
Votes
0
Comments