-
Bug
-
Resolution: Resolved Locally
-
Medium
-
None
-
1.2.7
NOTE: This bug report is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding bug report.
Hi - you've introduced a new field onto all Service Desk, giving the Customers the ability to log a ticket on behalf of someone else - "Raise this request on behalf of" ...
This was needed and I applaud that you've created it and deployed it - but I have had to create a field in the meantime to fulfill this role - "Call Originator". This is inbuilt into my dashboards and MI work for the company, to monitor who is raising calls on behalf of other people.
I have checked and I cannot add your new field to any of my Issue filters or dashboard views, so instead I need this field to be removable from my Customer Portal pages as I my customers to use the "Call Originator" field instead. But guess what - you've hardcoded it onto the page so I cannot remove it.
HELP! Can you please show how I can remove this asap as I am suddenly getting people complain about duplicate fields, not using the field I need for MI purposes and generally not happy about the Portal. This is damaging MONTHS of work to get this into my company and get people using it.
- is related to
-
JSDSERVER-1969 Warning Alerts for permission scheme should be dismissable
-
- Closed
-
-
JSDSERVER-1045 Make an ability to raise requests on behalf of your customers optional
- Closed
-
DESK-4139 Failed to load
- relates to
-
JSDCLOUD-1285 New field on Service Desk - I cannot hide it!
-
- Closed
-
Form Name |
---|
[JSDSERVER-1285] New field on Service Desk - I cannot hide it!
Workflow | Original: JSD Bug Workflow v5 - TEMP [ 2304584 ] | New: JAC Bug Workflow v3 [ 3125046 ] |
Status | Original: Done [ 10044 ] | New: Closed [ 6 ] |
Workflow | Original: JSD Bug Workflow v5 [ 2058428 ] | New: JSD Bug Workflow v5 - TEMP [ 2304584 ] |
Workflow | Original: JSD Bug Workflow v5 - TEMP [ 2055487 ] | New: JSD Bug Workflow v5 [ 2058428 ] |
Workflow | Original: JSD Bug Workflow v5 [ 1956135 ] | New: JSD Bug Workflow v5 - TEMP [ 2055487 ] |
Workflow | Original: JSD Bug Workflow v4 [ 1614794 ] | New: JSD Bug Workflow v5 [ 1956135 ] |
Description |
Original:
Hi - you've introduced a new field onto all Service Desk, giving the Customers the ability to log a ticket on behalf of someone else - "Raise this request on behalf of" ...
This was needed and I applaud that you've created it and deployed it - but I have had to create a field in the meantime to fulfill this role - "Call Originator". This is inbuilt into my dashboards and MI work for the company, to monitor who is raising calls on behalf of other people. I have checked and I cannot add your new field to any of my Issue filters or dashboard views, so instead I need this field to be removable from my Customer Portal pages as I my customers to use the "Call Originator" field instead. But guess what - you've hardcoded it onto the page so I cannot remove it. HELP! Can you please show how I can remove this asap as I am suddenly getting people complain about duplicate fields, not using the field I need for MI purposes and generally not happy about the Portal. This is damaging MONTHS of work to get this into my company and get people using it. |
New:
{panel:bgColor=#e7f4fa} *NOTE:* This bug report is for *JIRA Service Desk Server*. Using *JIRA Service Desk Cloud*? [See the corresponding bug report|http://jira.atlassian.com/browse/JSDCLOUD-1285]. {panel} Hi - you've introduced a new field onto all Service Desk, giving the Customers the ability to log a ticket on behalf of someone else - "Raise this request on behalf of" ... This was needed and I applaud that you've created it and deployed it - but I have had to create a field in the meantime to fulfill this role - "Call Originator". This is inbuilt into my dashboards and MI work for the company, to monitor who is raising calls on behalf of other people. I have checked and I cannot add your new field to any of my Issue filters or dashboard views, so instead I need this field to be removable from my Customer Portal pages as I my customers to use the "Call Originator" field instead. But guess what - you've hardcoded it onto the page so I cannot remove it. HELP! Can you please show how I can remove this asap as I am suddenly getting people complain about duplicate fields, not using the field I need for MI purposes and generally not happy about the Portal. This is damaging MONTHS of work to get this into my company and get people using it. |
Link |
New:
This issue relates to |
Labels | Original: affects-server vc | New: affects-cloud affects-server vc |
Labels | Original: vc | New: affects-server vc |
Workflow | Original: JSD Bug Workflow v2 [ 1602093 ] | New: JSD Bug Workflow v4 [ 1614794 ] |