 romainq
|
4213583ec8
Customer portal: adjusted the versions of the recently updated module (inc. the XML format version raised to 1.3)
|
9 years ago |
 glajarige
|
10309f0641
Portal : Datamodel modifications to ensure setup modularity
|
9 years ago |
|
romainq
|
3cdc918779
User request (all-in-one): the end-user can leave the request type undefined, in such a case, she can select any type of services and the request type gets computed when the requests is written to the DB. Still, this is possible to select a request type and the list of services is filled with the corresponding services. This behavior was necessary for the new user portal to work fine.
|
9 years ago |
 dflaven
|
10a57a267a
Prevent infinite cross-ticket recursion when propagating parent->child resolution in tickets.
|
9 years ago |
|
romainq
|
7f46108d88
New type of attribute: AttributeMetaEnum.
|
9 years ago |
|
dflaven
|
7e83561eb7
Impact analysis enhancement:
|
10 years ago |
|
dflaven
|
a886de7dbb
Impact analysis diagram is now considered as beta !
|
10 years ago |
|
dflaven
|
bf800862db
Relations & Impact analysis enhancements:
|
10 years ago |
|
dflaven
|
76a43b3264
Integration of the new impact analysis into the tickets.
|
10 years ago |
|
dflaven
|
4fa6ce55c4
Make sure that 'source' nodes for ComputedImpactedItems are not added twice to the ticket.
|
10 years ago |
|
dflaven
|
2c4841693c
Integration of the new way to compute relations into the datamodel (ComputeImpactedItems)
|
10 years ago |
|
romainq
|
fe85e87a4f
XML Modelization of the relations: fixed a bug in the compiler and transformed the datamodel files (2.x) into the latest 1.2 format
|
10 years ago |
|
dflaven
|
d7a6e7bcb5
#1037: refresh "priority" when either "impact" or "urgency" changes.
|
10 years ago |
|
dflaven
|
fededdb2e3
Add the appropriate "type" to the parameters passed to the actions on transitions.
|
10 years ago |
|
romainq
|
6c4addbe02
#1026 CSV import of tickets with impact = '', issuing a Notice
|
10 years ago |
|
romainq
|
91fc691764
#1029 Got rid of tags <format> that were not used at all and that were really misleading extension developers
|
10 years ago |
 etaloc
|
2c67afb8bd
update highlight scale for request-management modules
|
10 years ago |
|
romainq
|
2566ec00cc
#1022 Do cascade the resolution of an incident to its child requests + rework of the lifecycle/actions to ease the extensibility (New handlers: Rest, Copy, SetCurrentDate, SetCurrentUser, SetElapsedTime)
|
10 years ago |
|
dflaven
|
39345cf0db
Fix of read_only flags for some attributes (previous verison had typos, i.e. "readonly" instead of "read_only", which made the factorisation of the state flags incorrect)
|
10 years ago |
|
romainq
|
5b46f1068e
#995 Make sure that tto/ttr passed gets set even if the CRON has not been run (and as soon as some overrun has been counted)
|
10 years ago |
|
romainq
|
7095d1bf48
XML: normalized the format (allows for implementing a quick diff algorithm)
|
10 years ago |
|
dflaven
|
3f82103451
- Migration of the XML files to the version 1.1 of the XML schema.
|
11 years ago |
|
dflaven
|
2f3a180cb0
New concept in the XML: HighlightScale to avoid overloading GetIcon and GetHilightClass...
|
11 years ago |
|
dflaven
|
87e4186cc6
Added an identifier on the transitions to allow a finer granularity for the deltas.
|
11 years ago |
|
romainq
|
b0c6c4aada
#955 Translated the label "Open Requests" in the welcome menu
|
11 years ago |
|
dflaven
|
f080016d81
#906 Better way to handle the lock in order to prevent duplicates in the numbering of Tickets. Note that the iTopMutex now supports re-entrancy inside the same PHP page.
|
11 years ago |
|
romainq
|
e9d7995b59
#918 TTO/TTR status "passed" gets reset when the stop watch is stopped (using the status "triggered" instead)
|
11 years ago |
|
dflaven
|
49e4c39664
Trac #890: Dispatch the defines in the proper modules to make sure that the portal works with all possible combinations of tickets.
|
11 years ago |
|
romainq
|
95bc0b3309
#888 Security on the portal incompatible with customizations (regression introduced in 2.0.2), now requires to define PORTAL_USERREQUEST_DISPLAY_QUERY and PORTAL_USERREQUEST_DISPLAY_POWERUSER_QUERY
|
11 years ago |
|
romainq
|
beba63a527
Portal: Removed the public log for the user request creation form (still available on the ticket details). That was already done in change [2828] for ITIL flavour.
|
11 years ago |
