Bug 1193042 - New support case steps should be blocked for who does not have 'Manage Support Cases' permissio
Summary: New support case steps should be blocked for who does not have 'Manage Suppor...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: JBoss Operations Network
Classification: JBoss
Component: Red Hat Access
Version: JON 3.3.1
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: ---
Assignee: Thomas Heute
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-02-16 12:58 UTC by Jeeva Kandasamy
Modified: 2016-08-12 13:36 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-06-09 14:42:40 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
error-message-screen (135.51 KB, image/jpeg)
2015-02-16 12:58 UTC, Jeeva Kandasamy
no flags Details

Description Jeeva Kandasamy 2015-02-16 12:58:54 UTC
Created attachment 992167 [details]
error-message-screen

Description of problem:
Create new support case steps should be blocked at the beginning itself for the user who does not have 'Manage Support Cases' permission. Currently It's allowing user to reach till submit button. On the click of submit user come to know he does not have permission to create support case.

It's showing error message once user clicked submit button.
Error 403 Forbidden Message: {"code":"403","message":"Contact is set to not manage cases"}

Error message should be user friendly. The current error message looks like more technical.

Version-Release number of selected component (if applicable):
JBoss Operations Network
Version : 3.3.0.GA Update 01
Build Number : ab9ebbd:884011b
GWT Version : 2.5.0
SmartGWT Version : 3.0p

How reproducible:
always

Steps to Reproduce:
1. Login in to JBOSS ON 3.3.1
2. Login in to 'Red Hat access' with the user, who does not have 'Manage Support Cases' permission.
3. Open new support case.


Additional info: Screen shot is attached.


Note You need to log in before you can comment on or make changes to this bug.