 romainq
|
ce9ddcb295
Refactoring: font awesome can be used by all the application
|
8 years ago |
|
romainq
|
a6f045aba6
Reincorporate font-awesome into the core
|
8 years ago |
 glajarige
|
da0260c569
N°653 Lifecycle flags can be defined on both states and transitions (Note: This is a beta version and need to be tested!)
|
8 years ago |
|
glajarige
|
d694f2b506
N°829 Portal: AttributeUrl was not clickable in the new portal
|
8 years ago |
|
glajarige
|
26082d918c
Portal: Refactor a security check to remove unnecessary security messages in error.log
|
8 years ago |
 dflaven
|
dafff4e8e0
Declare the ApplyStimulus method, for use by the Designer.
|
8 years ago |
 cisou
|
20aff3a11e
Readme iTop Community 2.3.4
|
8 years ago |
|
cisou
|
05b85f1858
LOCK TABLE MySQL privilege is required for iTop user to restore backups.
|
8 years ago |
|
glajarige
|
c8f89e67a3
Internal: Added comment about portal logo priority order
|
8 years ago |
|
romainq
|
5d604448c9
N.816 New parameter in the working time computer GetDeadline API: the 4th parameter is the threshold for which the deadline is being computed.
|
8 years ago |
|
romainq
|
231732afdd
N.755 Case log preset by object copier is not correcly displayed in the object creation form (if combined with the copy of the previous log AND if that log has at least one entry). Has never worked.
|
8 years ago |
|
glajarige
|
8e170324b3
N°637 Portal: Better feedback on exceptions and user session timeout on AJAX calls
|
8 years ago |
|
romainq
|
cd93835ed7
N.417 Object name displayed with html entities (e.g. "&" shown as "&") when selecting/creating an object into an autocomplete
|
8 years ago |
|
romainq
|
4ada1cc5c2
N.689 61 tables limit. INVESTIGATING the issue. Added a test to reproduce the issue on the standard data model, and a test to build statistics on the number of tables used by classes.
|
8 years ago |
|
romainq
|
544e145058
Automatic test suite: fixed warnings (benchmarked queries processed instantaneously);
|
8 years ago |
|
romainq
|
449a39032a
N.755 Case log latest entry preset with a copy of a case log coming from another ticket. The log gets corrupted after adding a new entry.
|
8 years ago |
|
glajarige
|
89264d1104
Portal: CaseLog fields value was kept in the form after object update instead of being reset.
|
8 years ago |
|
romainq
|
c80fa95d2c
N.755 Case log latest entry preset with HTML code gets transformed into pure text
|
8 years ago |
|
glajarige
|
fba73bf449
N°807 Portal: add_to_list can now be used in action rules (Note: Works only for IndirectLinkedSet, not LinkedSet)
|
8 years ago |
|
glajarige
|
c090ae3838
Portal: Fixed friendlyname fields rendered as mandatory when they should have been readonly.
|
8 years ago |
|
romainq
|
429054bf3a
N.755 (reduces the impact) Core API: Fixed the merging of several entries into a case log (calling several times DBObject::Set for a case log). The previous implementation did not work at all, leaving the data structure inconsistent. Moreover, the last text given is now inserted AFTER the text it is merged with (not on top of it) like in a normal text stream.
|
8 years ago |
|
dflaven
|
8741689688
N°686 - protect the edition of dashboards against a no-longer-existing class.
|
8 years ago |
|
romainq
|
a87d98cf63
N.447 Impact analysis: messing up redundancy settings (could either lead to wrong results or a fatal error if a relation is configured downstream)
|
8 years ago |
|
glajarige
|
54d4ba5074
N°806 Portal: Wrong form used in some inheritance cases.
|
8 years ago |
|
romainq
|
3681a6a896
Fixes a regression introduced in [r4642]. N.450 Impact analysis. The previous fix aimed at generating more redundancy nodes, but in fact it generated too many in some circumstances.
|
8 years ago |
|
glajarige
|
d338d8269b
DBObject::ExecActions : add_to_list action now accepts the source object id as first parameter
|
8 years ago |
|
cisou
|
ba8004fc4a
n°519 add examples to REST/JSON on updating CaseLog with Text format
|
8 years ago |
|
romainq
|
256616a393
N.788 Impact analysis: graph not refreshed when trying to filter out some classes. The node removal algorithm has been improved in two places. 1) Do not create loops (i.e. an edge having both ends on the same node) when removing a node. 2) Correctly cleanup nodes having a loop (in case there is a loop in the original graph (defensive programming)
|
8 years ago |
|
romainq
|
08cea3a033
N.450 Impact analysis : missing edges (and redundancy) when two classes impact a given class and both relations use the same neighbour id (and if redundancy is enabled over both relations)
|
8 years ago |
|
glajarige
|
58f6caa386
N°800 Portal: log_kpi_duration / log_kpi_memory are now supported by the portal
|
8 years ago |
