Bug 487338 - Move Partner Create Case Entitlement out of Legacy Entitlements
Summary: Move Partner Create Case Entitlement out of Legacy Entitlements
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Issue-Tracker
Classification: Retired
Component: Security/Permissions
Version: Next Ops Maint
Hardware: All
OS: All
high
low
Target Milestone: ---
Assignee: Issue-Tracker Bug Watch List
QA Contact:
URL:
Whiteboard:
Depends On: 454775
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-02-25 14:58 UTC by Mike Amburn
Modified: 2010-09-24 20:24 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 454775
Environment:
Last Closed: 2010-09-24 20:24:05 UTC
Embargoed:


Attachments (Terms of Use)

Description Mike Amburn 2009-02-25 14:58:39 UTC
+++ This bug was initially created as a clone of Bug #454775 +++

This addresses the current feature that allows partners to enter a case on
behalf of a customer. This is currently made available via a legacy entitlement
called Partner Case Management.

Rather than permission them individually via legacy entitlements, suggested
solution is to move this to group level permissions in I-T db.
Allow a group to be designated as a "Partner" via the I-T UI, and then associate
them to customer groups by adding those Customers to that Group.
Allow logins to be created for the Partner employees that would allow the
Partner to login to the CSP and open a case on behalf of the customer.
Allow logins for the Partner employees to view and update cases inside of Issue
Tracker UI.
Add tiers to comment permissions so that instead of public/private we have
customer visible/partner&customer visible/partner & RH visible/RH only
Any case created by the customer via their own login would be visible to the
partner.
Cases created by the partner on their own but not on behalf of a customer should
not be visible to the customer(s).
Partner logins should be able to subscribe to events for any customer case.

----

Moved from Jira (JBNET-2391)

Comment 1 David Spalding 2010-09-24 20:24:05 UTC
This bug hasn't been revisited in 18 months ... closing now that Rosetta is out.


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