This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.
You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

WHAT WE'RE WORKING ON FOR SWSD (UPDATED OCTOBER 15TH, 2020)

Strengthening the ITSM Core  

  • Change Management:  
    • Request a Change from the Portal  
    • Reoccurring / scheduled Changes  
  • Notifications: Advanced management capabilities   
    • Expand notifications support to additional ITSM objects  
    • Exclude group notifications  
    • Daily email digest  
  • Ticket Templates: Be able to have pre-filled tickets for quicker ticket creation time  
  • Custom State Colors and Portal Name: Ability to change the state color and customize the state name on the portal  
  • Dynamic Forms:  provide an efficient way to collect and validate inputs that are context dependent 
  • Application menu – a docked, left side menu for easier and faster access to menu options 

Analytics  

  • Dashboard Enhancements:  
    • Advanced filtering in the incident's widgets  
    • Ability to Change the widget view and ‘group by’ selection in the incident's widgets 
    • New widgets to cover Service Statistics  
    • Ability to create a custom widget from the incident data   
  • Reports Enhancements:   
    • Adding new reports: 
      • Advance Service Statistics 
      • Open-tickets age distribution  
    • Enhancing existing reports and report’s functionality: 
      • CSV output option for scheduled reports 
      • Making the 'Manual Time Tracking' reports clickable so you can better understand how the time was spent  
  • New filtering capabilities   
  • PowerBI connector 

 

Workflows and Automation  

  • Automation rules: Create records   

Service Engagements  

  • Mobile:  
    • Other assets 
    • Change management  
    • Tasks & approvals access for service task users 
  • Portal:  
    • Introduce components which display different types of data  
    • Ability to customize the layout of your portal by adding/removing and resizing components  
  • Integrations: 
    • Integrate with Microsoft Teams for creating new incident tickets 

Admin & Setup  

  • Re-organize the setup menu: Separate first-time setup items from the daily administration of application preferences (e.g. automations, email templates, etc.).  
  • Delegate admin functions: Allow admins to add roles with select setup privileges  

  

Discovery  

  • Jamf integration – import asset information from Jamf (Apple devices) 
Parents
  • The removal of access to the Ideas page (previously used for customer feedback and voting purposes) is a step backward IMHO.

    I used the Chat function to indicate that the Change request forms need the same notification functions for Notes and Approver comments, which otherwise sit there unnoticed.  Apparently that request had 3 votes before the Ideas page was removed from public view.  Now we (customers) cannot understand the process by which the next "Idea" is chosen and progressed.  So be it, but please put it on the roadmap to align the interfaces consistently.  Change requests Notes also don't have the @username function - just make them Comments instead so we can react to challenges to the Change Request - we have hundreds, and currently it's a manual check - that's surely not intended by the dev team?

Reply
  • The removal of access to the Ideas page (previously used for customer feedback and voting purposes) is a step backward IMHO.

    I used the Chat function to indicate that the Change request forms need the same notification functions for Notes and Approver comments, which otherwise sit there unnoticed.  Apparently that request had 3 votes before the Ideas page was removed from public view.  Now we (customers) cannot understand the process by which the next "Idea" is chosen and progressed.  So be it, but please put it on the roadmap to align the interfaces consistently.  Change requests Notes also don't have the @username function - just make them Comments instead so we can react to challenges to the Change Request - we have hundreds, and currently it's a manual check - that's surely not intended by the dev team?

Children
No Data