-
Suggestion
-
Resolution: Low Engagement
-
0
-
1
-
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
I need a filter that will show issues which has been updated since the last time i saw them. The solution would be : updated > lastViewed.
- is duplicated by
-
- Closed
- is related to
-
- Closed
-
- Gathering Interest
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JRACLOUD-45020] Filter showing issues that has been updated since lastViewed
If anyone else is still searching and/or waiting for a solution to this, after some searching I found that there is a built-in "last updater/commenter" field, which can be added to issues as a custom field (Settings -> Fields -> Custom Fields -> Add -> Advanced).
This can be compared to "currentUser()" or filtered as "not an agent" etc, making it possible to only see issues that have been updated by someone else.
Another slightly more limited possibility is a boolean flag field "last commented by a user" found in the same place.
Wratko Hlavina
added a comment - You have a related and broader feature request to support arbitrary date comparisons (JRA-20727). Unfortunately, it remains open since 2010.
There's a lot of people (in our group, in particular) who would appreciate getting the list of issues which were updated after last viewed. The ability to track what's new is our primary use case for sending email notifications from JIRA and using that instead of the JIRA interface.
If JRA-20727 is too hard to implement, can you please consider solving the specific case of supporting updated > lastViewed in JQL?
It would be even better to expose a read/unread flag on JIRA issues, and increase the jira.max.Issue.history.items so that users could rely on the flag to keep abreast of what's new.
So far, the discussion on JRA-20727 recommends using Script Runner as workaround. Unfortunately, Script Runner doesn't hadle updated > lastViewed. See Adaptavist's feature request SRJIRA-1101.
Wratko Hlavina
added a comment - You have a related and broader feature request to support arbitrary date comparisons ( JRA-20727 ). Unfortunately, it remains open since 2010.
There's a lot of people (in our group, in particular) who would appreciate getting the list of issues which were updated after last viewed. The ability to track what's new is our primary use case for sending email notifications from JIRA and using that instead of the JIRA interface.
If JRA-20727 is too hard to implement, can you please consider solving the specific case of supporting updated > lastViewed in JQL?
It would be even better to expose a read/unread flag on JIRA issues, and increase the jira.max.Issue.history.items so that users could rely on the flag to keep abreast of what's new.
So far, the discussion on JRA-20727 recommends using Script Runner as workaround. Unfortunately, Script Runner doesn't hadle updated > lastViewed . See Adaptavist's feature request SRJIRA-1101 .
Hi everyone,
Thank you for bringing this suggestion to our attention.
As explained in our new features policy, there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritize and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order.
Unfortunately, as a result of inactivity (no votes or comments for an extended period of time), this suggestion didn’t make it to the roadmap and we are closing it.
While this issue has been closed, our Product Managers continue to look at requests in https://jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket.
Thank you again for providing valuable feedback to our team!