-
Incident Queue
Incident queue will allow the operation to be continuously assigned to new user without waiting for incident response. this should decrease incident response time to Minimum, it can be done by adding users that has eye on screen role continuous ti...
3
Not under consideration
-
Prepare list of available Substitution Values in Notifications
I faced with a lack of information about available Substitution Values. I know that System is flexible and has wide variety of using Substitution Values, but it is not described anywhere except for this link. I think it would be great to have a l...
0
Future consideration
-
National Language Supports of log display function in In-Product Script
In-Product Script (Customization Settings > Scripts) has the capability to test a script with [>Run] button. Support the following script: log.info("{}".format(incident.description.content)) This script s...
1
Not under consideration
-
ActiveMQ also suppports the MQTT protocol for asynchronious integrations. Can this be used when implementing ActionModules instead of the currently used STOMP protocol with the delivered Python based Framework?
MQTT is more generally supported. MQTT is supported by IBM MQ.. STOMP is not (I think) We would like to 'secure' the API using an API Gateway. MQTT is supported, STOPM is not!.
0
Not under consideration
-
Ability to Select existing Tabs show on a Task Bar
The ability to Select existing Tabs (incident Layouts: Details, Artifacts, other) show on a Task Bar would be very helpful, and time saving as it would allow the User to stay in a Task, Rather than having to jump back and forth between the inciden...
1
Not under consideration
-
Add nano to RHEL
Nano text editor was available on Debian and is a more user friendly alternative to vi. Can this be added to RHEL?
2
Not under consideration
-
User interaction - Tracking and analysis (similar to Adobe Analytics or Google Analytics)
We require metrics in terms of application use, such as how many times certain pages are visited, time spent on page or within the application, time logged in and similar metrics. This is required to know whether analysts use the application as e...
1
Not under consideration
-
Displaying ID in the Console
Currently, from the Console, I can see Incident ID (inc_id) either on the List Incidents or Detail page.Unfortunately, from the Console, we cannot see other IDs, such as user_id, group_id, role_id, script_id, phase_id, task_id, etc.These ID value ...
3
Not under consideration
-
Self contained workspace
In the current configuration, if I add a mandatory field in the first page of the Layout, that field will be showing up and enforced on any incident types, in which it is not needed on other incident types. If I put that mandatory field in the sec...
0
Not under consideration
-
Create additional Default Notifications
When Incident/Task Attachments added When Incident/Artifact relationships are made
1
Not under consideration