Only thing I can think of is a calculation on the user. Create a -1 length string attribute and then after you create an incident have it write a string with line feeds to the user attribute with the history you want. Possibly a trigger may be even better. Because it is on the User object, you will be able to display it after the RaiseUser is selected.
Now that I think of it, this is how I will solve my own long standing issue. I always wanted to know if a user has outstanding incidents. We create lots of duplicates. I could use my own suggestion and have a window that lists open incidents. In 7.6 I could even hide the attribute if empty.
Thanks for the help. Time to write a calculation now.
I'm glad I could spark an idea.
Let us know how the calculation works for you. and share the detail once done. Thanks
I mamanged to get this working by creating Filters for Incidents and Requests and including them onto a Call module window i created.
Follow the link below:
Filter should be Based On Incident or Request Module and Filter by Call Module.
Criteria should be Raise User is Equal to (RaiseUser)
What I've done is create and add a new filter based on Process, that way you can include everything (I/P/R/C/task) associated with that user. If you only want Incidents/Requests, then you can specify extra criteria on the Class or ID ranges (etc.) to narrow it down and exclude Tasks and such.
Here's what it looks like in use:
And the filter itself is straightforward:
Once designed and saved, just drop the new filter onto the Collections area of the window and set to Display on Tab.