-
Suggestion
-
Resolution: Won't Do
-
None
-
None
NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.
Currently Confluence renders the last n pages that match a user's feed. This can cause problems when users have feeds that show the last 100 updated pages and request that every 15 minutes. This is resource intensive even if they are simple pages.
As the amount of content increases in a confluence instance, users who want to keep up with many spaces tend to increase the item limit and shorten the duration between updates so they don't miss out on new pages/blog posts/comments. This is not scaling very well for us.
It would be nice if there is an option in the feed builder to see "only give me pages that have changed since I last checked the RSS feed". That way, even if users check their feeds every 5 miutes, confluence only has to do a (relatively easy) "last modified since" check rather than render the last 100 posts.
- relates to
-
- Gathering Interest
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[CONFSERVER-18633] Have a setting in the feed builder to only show pages updated since last check
JP Cornelissen
added a comment - If not since the last check then once every xxx hours. I now see that the RSS feed get's 5 entries when 5 changes were made to the same page in a short period of time. It should reconcile multiple page changes into a single RSS entry per day. Or even better, the RSS feed builder should have a setting where you can indicate you want reconciliation take place once per xx hours.
JP Cornelissen
added a comment - If not since the last check then once every xxx hours. I now see that the RSS feed get's 5 entries when 5 changes were made to the same page in a short period of time. It should reconcile multiple page changes into a single RSS entry per day. Or even better, the RSS feed builder should have a setting where you can indicate you want reconciliation take place once per xx hours. Any hit on that particular user's RSS feed means it gets marked as read till that time.
Means what gets marked as read? I could see a solution working like this:
- if the "only serve new content" option is checked, Confluence stores the last time a particular feed URL was served to a particular user
- when serving up that feed URL, Confluence only retrieves and renders content which was updated after that timestamp.
If it's optional, we might be able to introduce such a feature. But I'm still concerned it won't work or will be very confusing for a huge number of our customers. Introducing options like that is not usually a good idea.
I don't think it needs to be over-engineered. Keep it simple. Any hit on that particular user's RSS feed means it gets marked as read till that time.
- Needs to only work for authenticated users
- Assume users to only use one reader
- Users can elect to get all posts or "only since last check"
This probably wouldn't work as you'd expect. If the same person used more than one RSS reader software, or the same software in multiple locations, you'd get some items showing up in one reader, and some in the other. Neither would have a complete list of posts, because the server only returns what it thinks that user has already seen.
I'm not sure there's a way to implement this that makes sense. Ideas and suggestions welcome.
Thank you for raising this suggestion.
We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now. Sometimes potentially valuable tickets do get closed where the Summary or Description has not caught the attention of the community. If you feel that this suggestion is valuable, consider describing in more detail or outlining how this request will help you achieve your goals. We may then be able to provide better guidance.
For more context, check out our Community blog on our updated workflow for Suggestions
Cheers,
Confluence Product Management