Bring a card that hasn't been addressed back to attention after a while

[AlexGuironnetRTE]

Some project users have expressed interest around the following use case:

• An operator receives a card from application A
• He/she doesn't get to address it right away, and it gets buried in the other incoming cards
• After a given while, the card is brought back to their attention by changing its severity to

An option would of course be for application A to keep track of the cards it sent and send an updated card after a while with the new severity, but it adds complexity on the application side and it clutters the OpFab archives with "meaningless" updates.

It could be useful in processes where there is some kind of service-level agreement (90% of requests addressed in less than 3 days for example). You want cards that are getting close to their deadline to be brought back to the top of the stack, but you don't want the response to be disabled even if you're a little past the deadline.

I'm not a big fan of using a severity change to show escalation and make the card move back up the feed. I think as a user I would prefer to be able to keep the distinction between something that's red "because it was orange but someone has been waiting on me for 10 minutes or maybe I'm about to go past the SLA" from red because it's a critical alert for a severe event. However, the severity change is a request from the end-users.

Note: This would be different from lttd (last time to decide) as it is specified as a delay from the publication date, and also because as described above it shouldn't disable actions.

@freddidierRTE could the reminder feature be used for this purpose?

What do you think?