The current implementation of RSS is very barebones (still happy that it exists!).
Problem
Right now if there is an update added to an incident the RSS feed will not be notified to reflect that.
Solution
As per the RSS 2.0 spec, you can create an "updated" RSS functionality by changing the guid (as per the spec here).
Contributing
I am willing to make a pull request with the desired functionality.
I am still between the solution of creating "perminant" items or "impermanent";
meaning if the rss file contains all the items (for all the incidents and its updates one seperate item)
or just the incident, and when an update is created we just update the item with a new guid. (the rss file returned only contains the incident with the information in the details)
I have created a fork with the second option implemented in a separate branch
Blocking?
I might want to wait on #256 so the notifications are not wrong (incident on new status while update on old status)
The current implementation of RSS is very barebones (still happy that it exists!).
Problem
Right now if there is an update added to an incident the RSS feed will not be notified to reflect that.
Solution
As per the RSS 2.0 spec, you can create an "updated" RSS functionality by changing the guid (as per the spec here).
Contributing
I am willing to make a pull request with the desired functionality.
I am still between the solution of creating "perminant" items or "impermanent";
meaning if the rss file contains all the items (for all the incidents and its updates one seperate item)
or just the incident, and when an update is created we just update the item with a new guid. (the rss file returned only contains the incident with the information in the details)
I have created a fork with the second option implemented in a separate branch
Blocking?
I might want to wait on #256 so the notifications are not wrong (incident on new status while update on old status)