Badges [ 6 ] [-]
Memberships [ 1 ] [+]
Activity Stream [+]
Ideas Contributed [ 26 ] [+]
I suggest to establish a filter in all Change Views to hide Changes in an END state
I suggest to enable the ordering of CIs and Services bye this cute little blue bubble (up/down)
I suggest to implement a copy function for change or workorder templates between two OTRS systems.
I suggest the implementation of service dependent forms instead of the traditional new ticket mask...
I suggest to add a "new" role to the Change Mgmt Module for notification purposes: RfCTicketOwner
As the RfCTicketOwner should stay the primary contact for the customer she/he needs to be kept updated about the change progress.
There might be even a ViewChange option for linked changes to his/her RfCs...
I suggest to make Ticket FreeTextFields accessable via Customer Portal (either in the NewTicket view or (better(!)) as a form/questionaire)
I suggest (not to rename the SysConfig) but to design it like the Windows(tm)(c)(r)(whatsoever) Registry - dreaming of a tree-structure ,.oO°'
I suggest to enable any configuration possible via the SysConfig
I'd like to have a dependency from a workorder to ANY CI (Service=CI) that would effect the "Incident State" or even "Deployment State" of this CI.
like: IF workorder "GMS-07 Set Mailserver on fire" = In Progress THEN set CI-IState to Warning"
I suggest a kind of Lock-State for the Change if it is succesful or in any other *END state.
For security/revision reasons this might be necessary.
Maybe this should not be ative for emergency changes, as the documentation may be made after the change is done but even then there might be some kind of "LOCK-button"
I suggest the implementation of different workorder state machines. - For different kinds of changes there seems to be the customer requirement for different WO state machines. Customers should be able to define this "kind of change" themselves - If sometime the state machine is changed this will a) affect all active templates and b) will have a very bad effect on the closed changes in terms of revision... as far as ...more »
To better overview complex changes I suggest either - the grouping of workorders and allow conditions to affect these or - to define dependencies between changes like "Change 1 needs to be succesful for Change 2 to start" What I would like to see is the following: - Be able to link Changes with Changes - Have all linked Change Numbers available in Conditions - Have all linked Change Numbers available in Conditions ...more »