Filters management - Cronologia

Renato.daverio: /* How To Create complex filter */

2018-10-16T10:07:44Z

‎How To Create complex filter

Renato.daverio: /* How To Create complex filter */

2018-10-16T10:07:20Z

‎How To Create complex filter

Renato.daverio: /* How To Create complex filter */

2018-10-16T10:06:09Z

‎How To Create complex filter

Renato.daverio il 10:03, 16 ott 2018

2018-10-16T10:03:11Z

Francesco.bertuletti: /* How To Create complex filter */

2018-06-21T12:15:27Z

‎How To Create complex filter

Francesco.bertuletti: /* How To Create complex filter */

2018-06-21T10:50:54Z

‎How To Create complex filter

Francesco.bertuletti il 10:33, 21 giu 2018

2018-06-21T10:33:58Z

Francesco.bertuletti: /* Primary and Secondary Section */

2018-06-21T10:27:12Z

‎Primary and Secondary Section

Francesco.bertuletti: /* Primary and Secondary Section */

2018-06-21T10:22:19Z

‎Primary and Secondary Section

Francesco.bertuletti: /* Primary and Secondary Section */

2018-06-21T10:16:56Z

‎Primary and Secondary Section

@@ Riga 256: / Riga 256: @@
   sg.resourceEntries as r where r.id =  ${securityContext.resourceId}))
-  '''Current User = Master SG Manager
+  '''Current User = Master SG Manager'''
-''' (main.masterSolutiongroup.id in (select sg.id from SolutionGroup as sg inner join
+ (main.masterSolutiongroup.id in (select sg.id from SolutionGroup as sg inner join
   sg.sgManagerEntries as r where r.id =  ${securityContext.resourceId}))

@@ Riga 234: / Riga 234: @@
 Some example:
-  # Current User = owner
+  '''Current User = owner'''
   (main.ownerId = ${securityContext.resourceId})
-  # Current user = Creator
+  '''Current user = Creator'''
   (main.resource.Id = ${securityContext.resourceId})
-  # Current User = PM
+  '''Current User = PM'''
   (main.project.id in (select prj.id from Project prj inner join prj.pmEntries as pm
   where pm.id =  ${securityContext.resourceId}))
-  # Current User = SGm
+  '''Current User = SGm'''
   (main.solutiongroup.id in (select sg.id from SolutionGroup as sg inner join
   sg.resourceEntries as r where r.id =  ${securityContext.resourceId}))
-  # Current User = SG Manager
+  '''Current User = SG Manager'''
   (main.solutiongroup.id in (select sg.id from SolutionGroup as sg inner join
   sg.sgManagerEntries as r where r.id =  ${securityContext.resourceId}))
-  # Current User = Master SGm
+  '''Current User = Master SGm'''
   (main.masterSolutiongroup.id in (select sg.id from SolutionGroup as sg inner join
   sg.resourceEntries as r where r.id =  ${securityContext.resourceId}))
-  # Current User = Master SG Manager
+  '''Current User = Master SG Manager
- (main.masterSolutiongroup.id in (select sg.id from SolutionGroup as sg inner join
+''' (main.masterSolutiongroup.id in (select sg.id from SolutionGroup as sg inner join
   sg.sgManagerEntries as r where r.id =  ${securityContext.resourceId}))
-  # Current User = Ticket Requester
+  '''Current User = Ticket Requester'''
   (main.requester.id = ${securityContext.resourceId})
-  # Current User = Ticket Worker
+  '''Current User = Ticket Worker'''
   where main.id in (select asT.id from Resource as r inner join r.assignedTicketEntries as asT
   where r.id = ${securityContext.resourceId})

@@ Riga 241: / Riga 241: @@
   # Current User = PM
-  (main.project.id in (select prj.id from Project prj inner join prj.pmEntries as pm where pm.id =  ${securityContext.resourceId}))
+  (main.project.id in (select prj.id from Project prj inner join prj.pmEntries as pm
   # Current User = SGm
-  (main.solutiongroup.id in (select sg.id from SolutionGroup as sg inner join sg.resourceEntries as r where r.id =  ${securityContext.resourceId}))
+  (main.solutiongroup.id in (select sg.id from SolutionGroup as sg inner join
   # Current User = SG Manager
-  (main.solutiongroup.id in (select sg.id from SolutionGroup as sg inner join sg.sgManagerEntries as r where r.id =  ${securityContext.resourceId}))
+  (main.solutiongroup.id in (select sg.id from SolutionGroup as sg inner join
   # Current User = Master SGm
-  (main.masterSolutiongroup.id in (select sg.id from SolutionGroup as sg inner join sg.resourceEntries as r where r.id =  ${securityContext.resourceId}))
+  (main.masterSolutiongroup.id in (select sg.id from SolutionGroup as sg inner join
   # Current User = Master SG Manager
-  (main.masterSolutiongroup.id in (select sg.id from SolutionGroup as sg inner join sg.sgManagerEntries as r where r.id =  ${securityContext.resourceId}))
+  (main.masterSolutiongroup.id in (select sg.id from SolutionGroup as sg inner join
   # Current User = Ticket Requester
@@ Riga 259: / Riga 264: @@
   # Current User = Ticket Worker
-  where main.id in (select asT.id from Resource as r inner join r.assignedTicketEntries as asT where r.id = ${securityContext.resourceId})
+  where main.id in (select asT.id from Resource as r inner join r.assignedTicketEntries as asT

← Versione meno recente		Versione delle 10:03, 16 ott 2018
Riga 232:		Riga 232:

	In Filter ''view'' differently from ''Personal'' view has the possibility to define <u>QL Expression </u> (Query Language). This way to filter ticket is delivered only to the Administrator due to the technical knowledge necessary to create then.		In Filter ''view'' differently from ''Personal'' view has the possibility to define <u>QL Expression </u> (Query Language). This way to filter ticket is delivered only to the Administrator due to the technical knowledge necessary to create then.
		+
		+	Some example:
		+	# Current User = owner
		+	(main.ownerId = ${securityContext.resourceId})
		+
		+	# Current user = Creator
		+	(main.resource.Id = ${securityContext.resourceId})
		+
		+	# Current User = PM
		+	(main.project.id in (select prj.id from Project prj inner join prj.pmEntries as pm where pm.id = ${securityContext.resourceId}))
		+
		+	# Current User = SGm
		+	(main.solutiongroup.id in (select sg.id from SolutionGroup as sg inner join sg.resourceEntries as r where r.id = ${securityContext.resourceId}))
		+
		+	# Current User = SG Manager
		+	(main.solutiongroup.id in (select sg.id from SolutionGroup as sg inner join sg.sgManagerEntries as r where r.id = ${securityContext.resourceId}))
		+
		+	# Current User = Master SGm
		+	(main.masterSolutiongroup.id in (select sg.id from SolutionGroup as sg inner join sg.resourceEntries as r where r.id = ${securityContext.resourceId}))
		+
		+	# Current User = Master SG Manager
		+	(main.masterSolutiongroup.id in (select sg.id from SolutionGroup as sg inner join sg.sgManagerEntries as r where r.id = ${securityContext.resourceId}))
		+
		+	# Current User = Ticket Requester
		+	(main.requester.id = ${securityContext.resourceId})
		+
		+	# Current User = Ticket Worker
		+	where main.id in (select asT.id from Resource as r inner join r.assignedTicketEntries as asT where r.id = ${securityContext.resourceId})

← Versione meno recente		Versione delle 12:15, 21 giu 2018
Riga 229:		Riga 229:


−	The administrator has to manage carefully the ~~flexibity~~ the tool give him because he/she can select a conflictual ~~choise~~, so the filter doesn't return any data.	+	The administrator has to manage carefully the flexibility the tool give him because he/she can select a conflictual choice, so the filter doesn't return any data.
		+
		+	In Filter ''view'' differently from ''Personal'' view has the possibility to define <u>QL Expression </u> (Query Language). This way to filter ticket is delivered only to the Administrator due to the technical knowledge necessary to create then.

← Versione meno recente		Versione delle 10:50, 21 giu 2018
Riga 220:		Riga 220:
	# Ticket where the logged user is Owner		# Ticket where the logged user is Owner
	# Ticket where the logged user is Ticket Worker		# Ticket where the logged user is Ticket Worker
		+
		+
		+	Filter2 : Extract all the Incident, Service request ticket without Owner, is implented:
		+	* Primary section: Ticket Types : Select two elements:
		+	# "Incident"
		+	# "Request Fulfilment"
		+	* Secondary section: Group : Select Ticket without Owner
		+
		+
		+	The administrator has to manage carefully the flexibity the tool give him because he/she can select a conflictual choise, so the filter doesn't return any data.

← Versione meno recente		Versione delle 10:33, 21 giu 2018
Riga 209:		Riga 209:
	\|<u>Text Search </u> \|\| '''''Text''''' \|\| Secondary \|\|This section enable the user to select one or more Text field and specify a "Search String" value''		\|<u>Text Search </u> \|\| '''''Text''''' \|\| Secondary \|\|This section enable the user to select one or more Text field and specify a "Search String" value''

		+	\|}

		+	==== How To Create complex filter ====

−	\|}	+	Complex filter will be created as a combination of Ticket parameter selection. For example:
		+
		+	Filter1 : Extract all the Incident ticket where I'm Owner or I'm Ticket Worker, is implented:
		+	* Primary section: Ticket Types : Select "Incident"
		+	* Secondary section: Group : Select two elements:
		+	# Ticket where the logged user is Owner
		+	# Ticket where the logged user is Ticket Worker

@@ Riga 192: / Riga 192: @@
 * Role on ticket
 For each group is possible to enable the "Group Sub option" to simplify the group selection.
-Ticket role filter management is based on resource role on ticket (e.g. Ticket where the logged user is Creator or Owner or Ticket Workr,ect.)
+Ticket role filter management is based on resource role on ticket (e.g. Ticket where the logged user is Creator or Owner or Ticket Workr,ect.) The roles selection list is devided in two sections. Ticket where the logged user is ... and Ticket Without ...
 |-
 |<u>Priority</u> || '''''Ticket Priority''''' || Secondary ||This section enable the user to filter the ticket based on Ticket Priority and its component (ticket impact and ticket priority)

@@ Riga 188: / Riga 188: @@
 |<u>Ticket Op Status</u> || '''''Ticket Statuses''''' || Primary || multiselected filter for ''ticket'' status
 |-
-|<u>Groups</u> || '''''Ticket Dynamic Groups''''' || Secondary || Multiselection ''Group'' of filter. For each group is possible to enable the "Group Sub option" to simplify the group selection.
+|<u>Groups</u> || '''''Ticket Dynamic Group/Role''''' || Secondary || This section enable the user to filter per
 |-
 |<u>Priority</u> || '''''Ticket Priority''''' || Secondary ||This section enable the user to filter the ticket based on Ticket Priority and its component (ticket impact and ticket priority)