Layton ServiceDesk - Implementing Project Management

From Layton Support
(Difference between revisions)
Jump to: navigation, search
(Completed section)
(Completed section)
 
Line 61: Line 61:
 
#If they will be associated with the project, Enable the top-level Request Type that has the project name. This will enable every sub-level Request Type. If not, make sure that it is not enabled.
 
#If they will be associated with the project, Enable the top-level Request Type that has the project name. This will enable every sub-level Request Type. If not, make sure that it is not enabled.
 
#Repeat this process with every Analyst.
 
#Repeat this process with every Analyst.
 +
 +
==Form Design==
 +
As certain elements of a standard form won't apply, like the ''End User'' field, consider '''[[Layton ServiceDesk - Configuring the System - Form Design|modifying the default form]]'''.
  
 
=Use=
 
=Use=
 +
Much of the use of a project-management Request is covered in the general usage of the Requests portion of the product. Here are some specific features that may apply to project management:
 +
 +
*Create Requests in '''[[Layton ServiceDesk - Logging a New Request Using the Web Interface|the normal manner]]''', using the project Request Class.
 +
*'''[[Layton ServiceDesk - Logging a New Task|Tasks]]''' can be used to accomplish smaller aspects of the work of a Request.
 +
*Requests can be '''[[Layton ServiceDesk - Logging a New Request Using the Web Interface#Spawn Request|spawned]]''', if a duplicate is required, for example, assigning the same or similar Request to two Analysts.
 +
 +
Please '''[https://client.laytontechnology.com/ contact Support]''' for help with detailed configuration and usage.

Latest revision as of 03:19, 15 February 2021

Btn back up.png Back to Contents

Contents

[edit] Overview

Layton ServiceDesk can be used to manage projects, using a combination of a project-specific Request Class, Request Types specific to that Request Class, Requests in that Request Class, and Tasks.

[edit] Configuration

[edit] Request Class

Go to Administration > Libraries > Request Classes.

[edit] Recommended Configuration

[edit] Properties

  1. Create a Request Class for the project.
  2. Configure these settings:
    1. Class: Name of the project
    2. Description: A brief description
    3. Reply Email: No value
    4. Add To New Analyst: Disable. It's unlikely that you would want every new Analyst to be assigned to this Request Class.
    5. Add To New End User: Disable. End Users will not be a part of this project.
    6. Close Request when Tasks Complete: Disable
    7. Dynamic Form Generator: Disable
    8. Create Forms:
      1. Analyst: Enable
      2. End User: Disable—End Users won't be using it.
      3. Spawn: Enable.

[edit] Request Types

Go to Administration > Libraries > Request Types.

[edit] Recommended Configuration

[edit] Properties

  1. Create a new top-level Request Type. All the Request Types that would be used with the project will be below this. It will be used as an organizational level to hold the Request Types that will be used.
  2. Configure these settings:
    1. Name: The same name used with the project Request Class
    2. Is Incident: Disable
    3. Request Class: The Request Class that is being used for the project, with the project name
    4. Default Priority: (None)
    5. Auto Populate Assigned Analyst: (None)
    6. Specify Analyst: No value
    7. Do Not Email: Disable
    8. Task Template: None
  3. Create the Request Types that will be used with the project as sub-level Request Types to the previous. Use these settings:
    1. Name: A meaningful name for the type of Request that it will be used with
    2. Is Incident: Disable
    3. Request Class: The Request Class that is being used for the project, with the project name
    4. Default Priority: At your discretion
    5. Auto Populate Assigned Analyst: At your discretion
    6. Specify Analyst: At your discretion
    7. Do Not Email: Disable
    8. Task Template: At your discretion

[edit] Request Class

  1. Go back to Administration > Libraries > Request Classes.
  2. For the project Request Class, click the Edit button Lsd btn edit 16px.png in the Request Type column to open the Request Type dialog.
  3. Disable every top-level Request Type (you don't have to expand and disable every sub-level Request Type), except for the one that applies to the project. Ensure that all the sub-level Request Types are enabled.
  4. Click the Save button Lsd btn save.png to close the dialog.

[edit] Analyst Configuration

Analysts need to be assigned to the project-management Request Class, and those who are not part of the project need to be unassigned.

  1. Go to Administration > Company Structure > Manage Analyst.
  2. For the first Analyst, click the Edit button Lsd btn edit 16px.png in the Skills column.
  3. If they will be associated with the project, Enable the top-level Request Type that has the project name. This will enable every sub-level Request Type. If not, make sure that it is not enabled.
  4. Repeat this process with every Analyst.

[edit] Form Design

As certain elements of a standard form won't apply, like the End User field, consider modifying the default form.

[edit] Use

Much of the use of a project-management Request is covered in the general usage of the Requests portion of the product. Here are some specific features that may apply to project management:

  • Create Requests in the normal manner, using the project Request Class.
  • Tasks can be used to accomplish smaller aspects of the work of a Request.
  • Requests can be spawned, if a duplicate is required, for example, assigning the same or similar Request to two Analysts.

Please contact Support for help with detailed configuration and usage.

Personal tools
Namespaces

Variants
Actions
Main Page
Online User Guides
General Support
Release Notes
Toolbox