MediaWiki API result

This is the HTML representation of the JSON format. HTML is good for debugging, but is unsuitable for application use.

Specify the format parameter to change the output format. To see the non-HTML representation of the JSON format, set format=json.

See the complete documentation, or the API help for more information.

{
    "batchcomplete": "",
    "continue": {
        "gapcontinue": "Remediation_services",
        "continue": "gapcontinue||"
    },
    "query": {
        "pages": {
            "33": {
                "pageid": 33,
                "ns": 0,
                "title": "Reading conventions",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "This wiki content has been written using the following reading conventions.\n\n{| class=\"wikitable\"\n! Item !! Convention !! Examples\n\n|-\n|Entities || ''Italic'' ||  ''Project'', ''service'', ''resource'', ''user''.  \n \n|-\n| Menu  functionalities || '''''Bold and italic''''' || '''''Services/Add New''''' refers to the functionality Add New available as a menu item in the submenu Services.\n \n|-\n| Commands || '''Bold'''  || '''Delete''' refers to the application command Delete.  \n \n|-\n| References  to fields || <u>Underlined</u> || <u>Name</u> refers to the field Name.  \n \n|-\n| Values of fields || \"Brackets\" || \"Henry\" refers to the content Henry of a field, for example <u>Name</u>.   \n \n|-\n| References to tabs or form areas || <u>''Italic and underlined''</u> || ''<u>Options</u>'' refers to the section or tab Options of a form.  \n\n|-\n| Relevant text which needs to be highlighted || <u>'''Bold and underlined'''</u> || '''<u>Relevant text.</u>''' \n\n|}"
                    }
                ]
            },
            "193": {
                "pageid": 193,
                "ns": 0,
                "title": "Release and Deployment Management",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "''[[Glossary|Release and Deployment Management]]'' process is supported by a ''[[Glossary|SM]]'' ''[[Glossary|workflow cartridge]]'' that enables the execution of the process according to the ITIL and ISO/IEC 20000 guidelines.\n\nOf course the preconfigured process (the ''[[Glossary|workflow cartridge]]'') is just an accelerator and the tuning / completion of the initial configuration will still be required. To this aim, the [[Workflow engine|Workflow Engine]] guide may be useful.\n\n'''<u>IMPORTANT NOTE</u>''': the configuration below is only one of the possible configuration to deal with the ''[[Glossary|release and deployment management]]'' process. The need for a different behaviour of the process may be fulfilled by simple changes of the configuration.\n\n== Operational model ==\nThe preconfigured process has the objective to facilitate and support the effective and efficient execution of ''[[Glossary|releases]]''. At the core of the process configuration is the following operational model.\n[[File:Release Management Operational Model v1.0.JPG|centre|thumb|800x800px|Release Management operational model]]\nThe requester, a service manager, an authorized member of the ''[[Glossary|service desk]]'' or a technical team member (e.g. a developer) or the [[Glossary|''change Management'']] process requires a new ''[[Glossary|release]]''. The release manager takes in charge it and assigns an owner who coordinates all the tasks needed to fulfil the ''[[Glossary|release]]''. If necessary, the owner requests the ''[[Glossary|releasee]]'' authorizations to the ''[[Glossary|change authority]]''. Finally, he/she activates the ''[[Glossary|deployment change]]'' process in order to complete the installation of the ''[[Glossary|release]]'' in a target environment (e.g. test, production).\n\n== Roles ==\nFor this process, the following organizational roles are defined:\n\n{| class=\"wikitable\"\n! Organizational role !! Description !! itmSUITE\u00ae role mapping\n\n|-\n|Requester || \n* Opens requests for ''[[Glossary|releases]]'' on behalf of himself/herself or for a third party\n||  This role is mapped on:\n* service managers (see after);\n* service desk members (system ''[[Glossary|resources]] ''with ''[[Glossary|user]] ''of ''[[Glossary|user type]] ''\"Resource\"; the login identifier of this ''[[Glossary|user]] ''is \"SDSpecialist\");\n* technical team members (see after).\n\n|-\n|Release Manager || \n* Receives and evaluates release requests\n* Assigns a release owner\n* May act as a release owner\n||  This role is mapped on the service manager(r) of the ''[[glossary|service]]'' on which the ''[[Glossary|release]]'' is requested.\n \n|-\n| Release owner ||\n* Requires ''[[Glossary|release]]'' approval to the change authority after its assessment is completed\n* Assign tasks to be performed to complete the ''[[Glossary|release]] ''(e.g. opens ''[[glossary|deployment changes]]'')\n*  Watches over and monitors the ''[[Glossary|release]] ''along all its life cycle ensuring target service levels are achieved\n* Activates escalation/ routing/ requests\n* Manages all the communications with the requester\n* Checks the implementation and sets the ''[[Glossary|releasee]] ''to completed\n* Closes the ''[[Glossary|release]] ''after completing the final checks\n|| This role is assigned to the manager of the ''[[glossary|group]]'' \"Release Management\"; the login identifier of this ''[[glossary|user]]''  is \"ReleaseManager\".  \n \n|-\n| Technical team member  ||A technical team member may first of all be a requester (see before). However he/she may play an active role in the preparation and installation of the release. In detail\n\n* He/she receives the notification on the assignment of an activity concerning a ''[[Glossary|release]] ''(e.g. conducting the assessment or designing/implementing it)\n\n* Carries out the assigned tasks\n* Notices when completed or unable to complete\n|| There are several technical teams predefined for different domains. The following table shows which ''[[Glossary|users]] ''are members of each team.\n\n{| class=\"wikitable\"\n! Domain !! ''[[Glossary|Group]]'' !! Member\n''[[Glossary|users]]''\n\n|-\n|Application management || \"Application Management\" || \"AppManager\"\n\"AppSpecialist\"\n\n|-\n|Personal devices management || \"Personal Management\" || \"PersonalManager\"\n\"PersonalSpecialist\"\n\n|-\n|Network management || \"Network Management\" || \"NetManager\"\n\"NetSpecialist\"\n\n|-\n|Server management || \"Server Management\" || \"ServerManager\"\n\"ServerSpecialist\"\n \n|}     \n \n|-\n| Technical team manager || \n* Receives the notification about the assignment of the ''[[Glossary|release]] ''to his/her team in order to implement it\n* Assign the member of his/her team who should work on it (this can be done by setting the ''[[Glossary|ticket worker]]'' or creating and assigning ''[[Glossary|ticket activities]]'')\n* Watches over and monitors the work of his/her team\n|| There are several technical teams predefined for different domains. The following table shows which ''[[Glossary|users]]'' are set as ''[[Glossary|solution group manager]]'' for each domain.\n\n{| class=\"wikitable\"\n! Domain !! ''[[Glossary|Group]]'' !! ''[[Glossary|Group manager]]''\n\n|-\n|Application management || \"Application Management\" || ''[[Glossary|User]] ''\"AppManager\".\n\n|-\n|Personal devices management || \"Personal Management\" || ''[[Glossary|User]] ''\"Personal Manager\".\n\n|-\n|Network management || \"Network Management\" || ''[[Glossary|User]] ''\"NetManager\".\n\n|-\n|Server management || \"Server Management\" || ''[[Glossary|User]] ''\"ServerManager\".\n \n|}  \n\n|-\n| Service manager ||The service manager may act as a requester of a ''[[glossary|release]]'' (see before). The service manager(s) of the ''[[glossary|service]]'' on which the ''[[Glossary|release]]'' is managed acts as the release manager(s).\n|| There are different service managers configured for specific ''[[Glossary|services]]''. See [[Incident Management#Services|Services]] section in this page for further information. \n\n|-\n| Change authority || \n* Approves the ''[[Glossary|release]]'' implementation\n* Approves the ''[[Glossary|releasee]]'' deployment\n|| This role is mapped based on the required authorization and ''[[Glossary|release]]'' classification.\n\nFor ''[[Glossary|release]]'' implementation authorization:\n{| class=\"wikitable\"\n! <u>Release Type</u> !! ''Change authority''\n\n|-\n|\"Emergency\" || Service manager\n\n|-\n|\"Minor\" || Service manager\n\n|-\n|\"Major\" || CAB\n \n|}\nThe CAB is mapped on a ''[[Glossary|group]]'': \"CAB\".\n\nFor ''[[Glossary|release]]'' deployment authorization:  \n{| class=\"wikitable\"\n! <u>Change Type</u> !! ''Change authority''\n\n|-\n|\"Emergency\" || Service manager\n\n|-\n|\"Minor\" || Release manager\n\n|-\n|\"Major\" || Service manager\n \n|}\n\n|}\n\n== Process ==\nAs for all ''[[Glossary|workflows]]'', new ''[[Glossary|releases]]'' can be created by using the ''[[Glossary|self service portal]]'', accessible by means of '''''Self Service''''' menu. \n\nThe following ''[[Glossary|requests]]'' which trigger a new instance of the ''[[Glossary|release and deployment management]]'' process are configured and available in the ''[[glossary|self service portal]]'':   \n\n{| class=\"wikitable sortable\"\n! Self service topic !! Self service category !! Self service request !! Authorized roles\n\n|-\n| \"Applications\" || \"Application Management\" || \"Release\" (open a ''[[Glossary|release]]'') ||Requesters\n\n|}\n\nA ''[[Glossary|release]]'' may also be automatically opened during the execution of the ''[[Glossary|change management]]'' process. \n\nA ''[[Get started with itmSUITE\u00ae|workflow]]'' is configured to support the ''[[Glossary|release and deployment management]]'' process. The ''[[Glossary|workflow]]'' is characterized by ''[[Glossary|workflow statuses]]'' and ''[[Glossary|workflow transitions]]''. The figures below illustrate the process. \n[[File:Change management Operational Model 1 of 3 v1.0 .jpg|centre|thumb|800x800px|Release management process (1 of 3).]]\n[[File:Change management Operational Model 2 of 3 v1.0 .jpg|centre|thumb|800x800px|Release management process (2 of 3).]]\n[[File:Change management Operational Model 3 of 3 v1.0 .jpg|centre|thumb|800x800px|Release management process (3 of 3).]]\nThe table below explains the meaning of each ''[[Glossary|workflow status.]] ''\n\n{| class=\"wikitable\"\n! Workflow status !! Description\n\n|-\n| \"Default\" || A preliminary status which is displayed when a ''[[Glossary|release]]'' is created. \n\n|-\n| \"Opened\" || The ''[[Glossary|release]]'' has been recorded. \n\n|-\n| \"Requested\" || The ''[[Glossary|release]]'' is confirmed and has been requested. \n\n|-\n| \"In Analysis\" || The ''[[Glossary|release]]'' assessment and planning is ongoing. \n\n|-\n| \"Implementation Approval Requested\" || The ''[[Glossary|release]]'' approval request for implementation is submitted to the change authority. \n\n|-\n| \"Approved\" || The ''[[Glossary|release]]'' is approved for implementation.  \n\n|-\n| \"Not Approved\" || The ''[[Glossary|release]]'' is not approved for implementation.  \n\n|-\n| \"In Progress\" || The ''[[Glossary|release]]'' implementation is ongoing.  \n\n|-\n| \"Ready for Test\" || The ''[[Glossary|release]]'' is ready for testing. In this status, a ''[[glossary|deployment change]]'' can be opened to install the ''[[glossary|release]]'' in a test environment. \n\n|-\n| \"In Test\" || The ''[[Glossary|release]]'' testing is ongoing.  \n\n|-\n| \"Deployment Approval Requested\" || The ''[[Glossary|release]]'' approval request for deployment is submitted to the change authority.  \n\n|-\n| \"Deployment Approved\" || The ''[[Glossary|release]]'' is approved for deployment. In this status, a ''[[glossary|deployment change]]'' can be opened to install the ''[[glossary|release]]'' in the live environment. \n\n|-\n| \"Completed\" || The ''[[Glossary|release]]'' is completed.  \n\n|-\n| \"Change Review\" || The ''[[Glossary|release]]'' review is ongoing.  \n\n|-\n| \"Cancelled\" || The ''[[Glossary|release]] ''is not confirmed and, therefore, cancelled.  \n\n|-\n| \"Suspended\" || The ''[[Glossary|release]] ''execution is temporarily suspended. In this status ''[[Glossary|service levels]]'' calculation are suspended too. \n\n|-\n| \"Aborted\" || The ''[[Glossary|release]]'' execution is aborted.  \n\n|-\n| \"Closed\" || The ''[[Glossary|release]] ''closure has been confirmed. \n \n|}\n\nAnd finally the table below explains the roles authorized to execute the ''[[Glossary|workflow transitions]]''.\n\n{| class=\"wikitable sortable\"\n! Source status !! Destination status !! Authorized executors !! Comment\n\n|-\n| \"Default\" || \"Opened\" || Requester\nservice manager. \n||See the ''[[Glossary|self service portal]]'' configuration previously described.\n\n|-\n| \"Opened\" || \"Requested\" || Requester, service manager, release manager. ||\n\n\n|-\n| \"Opened\" || \"Cancelled\" || Requester, service manager. ||\n\n|-\n| \"Requested\" || \"Opened\" || Requester, service manager, release manager. ||\n\n|-\n| \"Requested\" || \"Cancelled\" || Requester, service manager, release manager. ||\n\n|-\n| \"Requested\" || \"In Analysis\" || Release owner, release manager. ||\n\n|-\n| \"Deployment Approved\" || \"Aborted\" || Release owner, release manager. ||\n\n|-\n| \"In Analysis\" || \"Requested\" || Release owner, release manager. ||\n\n|-\n| \"In Analysis\" || \"Approval Requested\" || Release owner, release manager. ||\n\n|-\n| \"In Analysis\" || \"Cancelled\" || Release owner, release manager. ||\n\n\n|-\n| \"Approval Requested\" || \"Approved\" || Change authority. ||Depending on ''[[Glossary|release]]'' classification (see [[DChange Management|roles]] for more details).\n\n|-\n| \"Approval Requested\" || \"Not Approved\" || Change authority. ||Depending on ''[[Glossary|release]] ''classification (see [[DChange Management|roles]] for more details).\n\n|-\n| \"Approval Requested\" || \"In Analysis\" || Release owner, release manager. ||\n\n|-\n| \"Not Approved\" || \"Cancelled\" || Release owner, release manager. ||\n\n|-\n| \"Approved\" || \"In Progress\" || Release owner, release manager, technical team member. ||\n\n|-\n| \"Approved\" || \"Suspended\" || Release owner, release manager. ||\n\n\n|-\n| \"Approved\" || \"Aborted\" || Release owner, release manager. ||\n\n|-\n| \"Suspended\" || \"In Progress\" || Release owner, release manager. ||\n\n|-\n| \"In progress\" || \"Suspended\" || Release owner, release manager. ||\n\n|-\n| \"In progress\" || \"Aborted\" || Release owner, release manager. ||\n\n|-\n| \"In progress\" || \"Ready for Test\" || Release owner, release manager technical team member. ||\n\n|-\n| \"In progress\" || \"In Test\" || Release owner, release manager, technical team member. ||\n\n|-\n| \"In progress\" || \"Deployment Approval Requested\" || Release owner, release manager. ||\n\n|-\n| \"In progress\" || \"Completed\" || Release owner, release manager. ||\n\n|-\n| \"Ready for Test\" || \"In Test\" || Release owner release manager, technical team member. ||\n\n|-\n| \"Ready for Test\" || \"Suspended\" || Release owner, release manager. ||\n\n|-\n| \"Ready for Test\" || \"Aborted\" || Release owner, release manager. ||\n\n|-\n| \"In Test\" || \"Deployment Approval Requested\" || Release owner, release manager. ||\n\n|-\n| \"In Test\" || \"Suspended\" || Release owner, release manager. ||\n\n|-\n| \"In Test\" || \"Aborted\" || Release owner, release manager. ||\n\n|-\n| \"Deployment Approval Requested\" || \"Deployment Approved\" || Change authority. ||\n\n|-\n| \"Deployment Approval Requested\" || \"Suspended\" || Release owner, release manager. ||\n\n|-\n| \"Deployment Approval Requested\" || \"Aborted\" || Release owner, release manager. ||\n\n|-\n| \"Deployment Approved\" || \"Completed\" || Release owner, release manager. ||\n\n\n|-\n| \"Completed\" || \"Change Review\" || Release owner, release manager. ||\n\n|-\n| \"Completed\" || \"Closed\" || Release owner, release manager. ||\n\n|-\n| \"Change review\" || \"Closed\" || Release owner, release manager. ||\n\n|-\n| \"Not Approved\" || \"In Analysis\" || Release owner, release manager. ||\n\n|}\n\n=== Related processes ===\nSeveral other ''[[Glossary|IT Service Management]]'' processes are related to the ''[[Glossary|release and deploymentmanagement]]'' one. Some basic interfaces are provided. The tab ''<u>Related Items</u>'' of the ''[[Glossary|release]]'' and, in particular, the sub tab <u>''Tickets''</u> of it allows to view all the existing relationships between the ''[[Glossary|release]]'' and other processes (managed through ''[[Glossary|tickets]]'').\n\n==== Incident management ====\nThe relationship is indirect: a ''[[Glossary|release]]'' may be related to ''[[glossary|changes]]'' which implement the solution of ''[[Glossary|incidents]]''. \n\n==== Problem management ====\nThe relationship is indirect: a ''[[glossary|release]]''  may be related to ''[[glossary|changes]]'' which implement the solution of ''[[glossary|problems]]''.\n\n==== Asset management and configuration management ====\nIt is possible to relate ''[[Glossary|configuration items]]'' to a ''[[Glossary|release]]'' by using the tab ''<u>Related Items</u>'' and, in particular, the sub tab <u>''Configuration Items''</u>. The ''[[Glossary|ASM]]'' and/or [[Glossary|''CMS'']] ''[[Glossary|modules]]'' features are made available here (e.g. view of ''[[Glossary|configuration item]]'' details, ''[[Glossary|configuration exploration]]'' or ''[[Glossary|impact analysis]]'').\n\n==== Change management ====\nA ''[[Glossary|release]]'' may include one or more ''[[Glossary|changes]].''  The relationship between a ''[[Glossary|release]]'' and and [[Glossary|change]] can be created from the ''[[Glossary|change]]'' but is is more frequently created working from the ''[[Glossary|release]]''. In any case, the relation from the ''[[Glossary|change]]'' can be created from the ''[[Glossary|tickets]]'' tab ''<u>Related Items</u> ''and, in particular, the sub tab ''<u>Configuration Items</u>'' by using the '''ADD EXISTING''' or '''SELF SERVICE''' commands. \n\n==== Deployment Change ====\nA ''[[glossary|deployment change]]'' may be opened automatically, by means of a command button and only in specific statuses (see the workflow statuses table above), in specific statuses of the ''[[glossary|release]]''. Once opened, the ''[[glossary|deployment change]]'' is kept linked to the ''[[glossary|release]]''.   <nowiki/>\n\n== Services ==\nDifferent ''[[Get started with itmSUITE\u00ae|services]]'' are configured for different ''[[Glossary|release]]'' domain areas as illustrated in the following table.\n\n{| class=\"wikitable\"\n! ''[[Glossary|Releases]]'' domain areas !! ''[[Glossary|Service]]'' !! ''[[Glossary|Service manager]]''\n\n|-\n|Application management || Only one application, and the related ''[[Glossary|service]]'' (\"itmCLOUD\") is configured. || The ''[[Glossary|user]]'' \"servicemanager\" is configured as ''[[Glossary|service manager]]''.\n\n|-\n|Personal devices management || \"Personal Device Management\". || The ''[[Glossary|user]] ''\"personalmanager\" is configured as ''[[Glossary|service manager]]''.\n\n|-\n|Network management || \"Network Management\" || The ''[[Glossary|user]] ''\"netmanager\" is configured as ''[[Glossary|service manager]]''.\n\n|-\n|Server management || \"Server Management\" || The ''[[Glossary|user]] ''\"servermanager\" is configured as ''[[Glossary|service manager]]''.\n\n|}\n\n== Management information ==\nMany management information are available as fields in the ''[[Glossary|release]]'' management configured form. The following table illustrates the intended use of key information and its behaviour. '''<u>NOTE</u>''': information are available (visible) and can be modified according to a specific configuration which is meant to be suitable for the organizational roles involved in the process. \n\n{| class=\"wikitable sortable\"\n! Information group or tab !! Field !! Purpose !! Comments\n\n|-\n| <u>''General Information''</u> || <u>Project/Service</u> || The ''[[Glossary|project]]'' or ''[[Glossary|service]]'' on which the ''[[Glossary|release]]'' is being managed. ||This is set at open time and cannot be changed later.\n\n|-\n| ''<u>General Information</u>'' || <u>Short Description</u> || To provide a short description of the ''[[Glossary|release]]''. ||Always visible.\n\n\n|-\n| <u>''General Information''</u> || <u>Creation Date</u> || To show the date and time the ''[[Glossary|release]]'' was created. ||This information is automatically recorded and cannot be manually changed. See ''<u>History</u>'' tab for more detailed tracking information.\n\n|-\n| <u>''General Information''</u> || <u>Last Update</u> || To show the date and time the ''[[Glossary|release]] ''was last updated. ||This information is automatically recorded and cannot be manually changed. See ''<u>History</u> ''tab for more detailed tracking information.\n\n|-\n| <u>''General Information''</u> || <u>Creation User</u> || To show the ''[[Glossary|user]]'' who created the ''[[Glossary|release]]''. ||This information is automatically recorded and cannot be manually changed. See ''<u>History</u> ''tab for more detailed tracking information.\n\n|-\n| <u>''General Information''</u> || <u>Update User</u> || To show the ''[[Glossary|user]]'' who updated the ''[[Glossary|release]]'' last. ||This information is automatically recorded and cannot be manually changed. See ''<u>History</u> ''tab for more detailed tracking information.\n\n|-\n| ''<u>Release Classification</u>'' || <u>Ticket Type</u> || To show the type of ''[[Glossary|workflow]]'' executed. ||This is automatically set at open time and can't be modified''.''\n\n|-\n| <u>''Release Classification''</u> || <u>Ticket Op Status</u> || To show the operational status of the ''[[Glossary|release]]'', see ''[[Glossary|workflow statuses]]'' in [[Release Management#Process|Process]] section of this page. ||Status changes are performed by means of the '''Save&Next''' command.\n\n|-\n| ''<u>Release Classification</u>'' || <u>Product</u> ||  This field allow to select one or more products which are released.\n||\n\n|-\n| ''<u>Release Classification</u>'' || <u>Target Environment</u> ||  This field allows to define the target environment where the ''[[Glossary|release]]'' is to be installed.\n||There could be more than one installation of the ''[[glossary|release]]'' in different environments (test, acceptance, live) managed with the ''[[glossary|deployment change]]'' process.\n\n|-\n| ''<u>Release Classification</u>'' || <u>Release Type</u> ||  This is the type of the release. \n||\n\n|-\n| ''<u>Release Classification</u>'' || <u>Release Number</u> ||  The number of the release.\n||\n\n|-\n| <u>''Management''</u> || <u>Supervising Team</u> || This field allows to define the supervising team for the release. ||\n\n|-\n| <u>''Management''</u> || <u>Release Team</u> || To define the team to which the'' [[Glossary|release]]'' is assigned for execution. ||\n\n|-\n| <u>''Management''</u> || <u>Release Owner</u> || To define who is the owner who should monitor the lifecycle of the ''[[Glossary|release]]''. ||\n\n|-\n| <u>''Release Details''</u> || <u>Description</u> || To provide a more detailed description of the ''[[Glossary|release]]''. ||An auto tracking field is used enabling to view the ''[[Glossary|user]]'' who has updated.\n\n|-\n| <u>''Release Details''</u> || <u>Comments</u> || To provide helpful comments. ||An auto tracking field is used enabling to view the ''[[Glossary|user]] ''who has updated.\n\n|}\n\nFields can be mandatory to save the ''[[Glossary|release]]'' in some [[Glossary|''workflow statuses'']]. These fields are highlighted with a red asterisk.\n\n== Views ==\nThe following ''[[Glossary|views]]'' are made available in the ''<u>Tickets</u>'' area of the home page:\n\n{| class=\"wikitable\"\n! View !! Content !! Requester !! Release owner !! Technical team !! Service manager !! Change authority !! Release Manager\n\n|-\n| Releases completed || ''[[Glossary|Releases]]'' in statuses \"Completed\", \"In Review\".  || X ||  || || X\n|| ||\n\n|-\n| Releass requested || ''[[Glossary|Releases]]'' in status \"Requested\".  ||  X\n||  \n|| ||X || ||X\n\n|-\n| Releases owned || ''[[Glossary|Releases]] ''in all the statuses but \"Opened\", \"Cancelled\", \"Aborted\", \"Closed\" where <u>Owner</u> is the logged ''[[Glossary|resource]].''  ||  ||  X || || || ||\n\n|-\n| Releases routed to my team || ''[[Glossary|Releases]]'' in all the statuses but \"Opened\", \"Cancelled\", \"Aborted\", \"Closed\" where the <u>Release Team</u> is the group to which the logged ''[[Glossary|resource]]'' belongs to.    ||  || || X || || ||\n\n|-\n| Releases assigned to me || ''[[Glossary|Releases]]'' in all the statuses but \"Opened\", \"Cancelled\", \"Aborted\", \"Closed\" where the <u>Ticket Worker</u> is the logged ''[[Glossary|resource]]''.    ||  || \n|| X || || ||\n\n|-\n| Releases suspended || ''[[Glossary|Releases]]'' in status \"Suspended\".    ||  || X\n||  ||X || ||X\n\n|-\n| Releases to review || ''[[Glossary|Releases]]'' in status \"Completed\" where <u>Release Type</u> is \"Emergency\" or where \"Major\".    ||  || X\n||  ||X || ||X\n\n|-\n| Releases to authorize for implementation || ''[[Glossary|Releases]]'' in status \"Implementation Approval Requested\".    ||  ||  ||  || ||X ||\n\n|-\n| Releases to authorize for deployment || ''[[Glossary|Releases]]'' in status \"Deployment Approval Requested\".    ||  || \n||  || ||X ||\n\n|-\n| Releases evaluated by Change Authority || ''[[Glossary|Releases]]'' in status \"Approved\" or \"Not Approved\".    ||  || X\n||  || X\n|| ||X\n\n|-\n| Changes approved for deployment || ''[[Glossary|Releases]]'' in status \"Deployment Approved\".    ||  || X\n||  || X\n|| ||X\n\n|}\n\nAdditionally, the following ''[[Glossary|views]]'' are made available in the '''''Release''''' menu for all the organizational roles:\n\n{| class=\"wikitable\"\n! View !! Content \n\n|-\n| Releases active || ''[[Glossary|Releases]] ''in all the statuses but \"Cancelled\", \"Aborted\", \"Suspended\", \"Closed\"\n\n|-\n| Releases suspended || ''[[Glossary|Releases]]'' in status \"Suspended\n\n|-\n| Releases closed || ''[[Glossary|Releases]]'' in status \"Closed\"\n\n|-\n| Releases cancelled || ''[[Glossary|Releases]]'' in status \"Cancelled\"\n\n|}\n\n== Notifications ==\nThe following ''[[Glossary|notifications]]'' are configured:\n{| class=\"wikitable\"\n! Trigger !! Recipients !! Purpose\n\n|-\n|A ''[[Glossary|release]] ''is requested || Release manager  || Alert that there is a ''[[Glossary|release]]'' to manage.\n\n|-\n|A ''[[Glossary|release]] ''is assigned a owner || Release owner || Alert that the ''[[Glossary|release]]'' was assigned to him/her.\n\n|-\n|A release team is assigned or changed for the ''[[Glossary|release]]'' || Release team || Alert that there are resource(s) to allocate to manage the ''[[Glossary|release]]''.\n\n|-\n|A ''[[Glossary|release]] ''review shall be executed (the ''[[Glossary|release]]'' is in ''[[Glossary|workflow status]]'' \"Release Review\") || Release owner, release manager || Alert that a ''[[Glossary|release]]'' review is to be done.\n\n|-\n|A ''[[Glossary|release]] ''is completed || The release'' ''creator, the requester || Alert that the ''release ''is deployed.\n\n|-\n|A ''[[Glossary|ticket worker]]'' is assigned || The assigned'' [[Glossary|ticket worker]]'' || Alert that there is work to be done.\n\n|-\n|A ''[[Glossary|release]] ''is suspended || The release'' ''creator, the requester, the service manager, the release manager, the releasee owner || Alert that the ''[[Glossary|release]] ''is suspended.\n\n|-\n|An ''[[Glossary|release ]]''is closed || The ''release ''creator, the requester, the service manager, the release manager, the change owner || Alert that the ''[[Glossary|release]]'' has been closed.\n\n|-\n|A ''[[Glossary|release]] ''is cancelled || The ''release ''creator, the requester, the service manager, the release manager, the change owner || Alert that the ''[[Glossary|change]]'' has been cancelled.\n\n|-\n|A ''[[Glossary|release]] ''implementation approval has been requested || Change authority || Alert that a ''[[Glossary|release]]'' implementation request has to be examined.\n\n|-\n|A ''[[Glossary|release]] ''implementation approval request has been examined || Release owner, release manager || Alert that the change authority has given a feedback on a ''[[Glossary|release]]'' implementation request.\n\n|-\n|A ''[[Glossary|release]] ''deployment approval has been requested || Change authority || Alert that a ''[[Glossary|release]]'' deployment request has to be examined.\n\n|-\n|A ''[[Glossary|release]] ''deployment approval request has been examined || Release owner, release manager || Alert that the change authority has given a feedback on a ''[[Glossary|release]]'' deployment request.\n\n|}\n\n== Reporting ==\nA set of standard reports are made available for the ''[[Glossary|release management]]'' process. It is not required to have the [[Glossary|REP]] ''[[Glossary|module]]'' to use them, however the [[Glossary|''module'']] is required if new or changed reports are needed. The available reports are placed under '''''Release/Reporting''''' menu.\n\nThe following table lists the reports available by default and their visibility:\n\n{| class=\"wikitable\"\n! Report name !! Content !! Access\n\n|-\n|Release per category - trend || An histogram showing the ''[[Glossary|release]]'' volumes per category (<u>Release Type</u>)monthly trend. || Release manager, service managers and technical team members.\n\n|-\n|Release per category - volume || A pie containing the split of ''[[Glossary|releases]]'' per category (<u>Release Type</u>). || Release manager, service managers and technical team members.\n\n|-\n|Release per service - trend || An histogram showing the ''[[Glossary|release]] ''volumes per ''[[Glossary|service]]'' monthly trend. || Release manager, servie managers and technical team members.\n\n|-\n|Release per service - volume || A pie containing the split of ''[[Glossary|releases]] ''per ''[[Glossary|service]]''. || Release manager, servie managers and technical team members.\n\n|-\n|Release per service/category - volume || An histogram showing the ''[[Glossary|releases]]'' volume per ''[[Glossary|service]]'' and category. || Release manager, service managers and technical team members.\n\n|-\n|Release - analysis time || A pie showing the percentage of ''[[Glossary|releases]] ''respecting the target defined for the \"Analysis time\"* ''[[Glossary|objective]]'' (the time elapsed from the \"Requested\" to the \"In Analysis\" ''[[Glossary|workflow status]]''. || Release manager, service managers and technical team members.\n\n|}\n<nowiki>*</nowiki> \"Analysis time\" is defined within the ''[[Glossary|OCE]]'' ''[[Glossary|module]]''.\n\nA basic form of reporting is also provided by ''[[Glossary|views]]. ''Views basically allow to list ''[[Glossary|releases]]'' and their attributes but may also be configured to calculates sums, averages on some of them.'' ''The available ''[[Glossary|views]]'' are illustrated in the dedicated [[Incident Management#Views|section]] of this page.\n\n== Examples of use ==\nIn this section some examples of use of the configured'' [[Glossary|release management]]'' process are given.\n\nIf you get lost, any time use the '''EXPLORE WORKFLOW''' command of the ''[[Glossary|release]]'' management form. This enables to view the status of the ''[[Glossary|workflow]]'' as shown in the figure below. By clicking on a relationship between ''[[Glossary|workflow statuses]]'', ''[[Glossary|roles]]'' and ''[[Glossary|users]]'' enabled to perform it are presented.\n[[File:Explore Workflow IM v1.0.JPG|centre|thumb|848x848px|Explore Workflow window]]\n'''<u>NOTE</u>''': the '''EXPLORE WORKFLOW '''command is available only if the ''[[Glossary|ticket]]'' is first saved.\n\nFor more information on how to use any workflows, including incident management, please refer to the [[workflow execution guide]].\n\n=== Create and request a new ''[[Glossary|release]] ''as a final user ===\n# Login as \"appspecialist\"\u00a0''[[Glossary|user]]''\n#  Activate the\u00a0'''''Self Service'''''\u00a0menu\n#  Choose a\u00a0''[[Glossary|self service topic]]'',\u00a0''[[Glossary|self service category]]''\u00a0and finally \"Release\" as\u00a0''[[Glossary|self service request]]\u00a0''(this determines the creation of a new ''[[Glossary|release]]'')\n#  Fill the\u00a0''[[Glossary|release]]''\u00a0form, at least with mandatory fields, and save with the\u00a0'''SAVE'''\u00a0command (the ''[[Glossary|release]]'' is now in ''[[Glossary|workflow status]]'' \"Opened\")\n# Set the ''[[Glossary|release]]'' in ''[[Glossary|workflow status]]'' \"Requested\" with the '''SAVE & NEXT''' command\nYou have now saved the\u00a0''[[Glossary|release]]'', take note of the\u00a0''[[Glossary|ticket]]''\u00a0number for further reference and use.  \n\n=== Assign a ''[[Glossary|release]]'' for analysis as a release manager ===\n#Login as \"releasemanager\"\n# Open the the desired ''[[Glossary|release]]''; you can do it quickly either by\n#* Access the \"Releases Requested\" ''[[Glossary|view]]'' in the ''<u>Tickets</u>'' area of the home page and pick a ''[[Glossary|release]] '' \n#* Access the '''''Release/Releases active '''''menu and pick a ''[[Glossary|release]] ''in'' [[Glossary|workflow status]] ''\"Requested\"'' ''among those listed\n#* Insert the reference number of a ''[[Glossary|release]]'' in ''[[Glossary|workflow status]]'' \"Requested\" in '''Quick Search''', after selecting the ''[[Glossary|search context]]'' \"Ticket\"\n# Assign the key roles \n#* Fill the ''[[Glossary|release]] ''form with <u>Release Owner</u>, <u>Release Team</u> and, may be, <u>Supervising Team</u> \n#*  Pressing the '''SAVE & NEXT''' command, choose the \"1. Assign ticket\" ''[[Glossary|workflow transition]] ''\nThe ''[[Glossary|release]]'' is now in ''[[Glossary|workflow status]]'' \"In Analysis\".[[Incident Management|<nowiki/>]]<nowiki/>"
                    }
                ]
            }
        }
    }
}