We recommend reviewing what is submitted before posting, in case your idea has already been submitted by another community member. If it has been submitted, vote for that existing feature request (by clicking the up arrow) to increase its opportunity of being added to Cireson solutions.
For more information around feature requests in the Cireson Community click here.
Add date/time Created and Last Modified to the WI form- easy visible
It is very time consuming to go to the History page every time you want to know when the WI was opened/created o last touched.
Comments
I have converted this to an idea and moved to portal feature request
In general we have been thinking adding a little bit more info to the WI form header, things that come to mind are, Title so that when I land on the activity tab I don;t have to jump back to the general tab to see what the WI is about, maybe even an option to reveal the full desc.
I like your ideas as well.
Let's see what the rest of the community thinks!
I Agree. Title would be nice as a header next to the ID#. I'm considering moving or having a copy of the User Input Area/Description under Activities page for easy reference.
I also would like to add "Created By" and "Modified By" if it's possible.
Looks like there is no direct property for the Last Modified by. I have had a look and found this link in the community.
https://community.cireson.com/discussion/1191/modified-by-user-in-the-work-item-overviews
For example:
This is just one of the fields--add the rest inside the div.headingFields element or split them into multiple divs.
And in your CSS:
The complete solution would look like this:
custom.js
custom.css
Which yields this result:
If you want it for other classes that IR, copy the whole code block in
custom.js
and replace'Incident'
in the first line with e.g.'ServiceRequest'
.No, problem! The next issue is getting the users who created, resolved and most complex, later updated the WI. The first two should be easily retrievable, at least the GUID, which then needs to be converted to an actual username.
The Last Modified is more complex, as you would need to get all changes, find the newest and get the user from there. And should it show updates by service accounts or not? Or maybe retrieve action log comments? But that would give inconsistencies between the Last Modified date and the username, if the update is done by a service account.
Just FYI, I had a look at the "by" fields, and only CreatedBy is easily accessible. The other two fields are not included directly on the WI object, so they would need to be accessed through the API. I feel like it would be to heavy an operation to do each time a WI form opens, which would probably slow down the load time, so I don't think it worth it.
Tom_Hendricks Are you running multiple portal servers as we found we had issues when we went live with the portal.
Now have a load balanced setup and encounter virtually no performance related issues.
For load balanced web servers, this also means installing another SCSM management server (one per web server), correct?