Labels

"Milestone Summary" portlet is not sorta
1
9.62 GUI installation
2
Ad
8
Adding Developer name field from Object type...
1
Admin
64
Admin Console
10
Agile
7
AlreadyInOctane
0
Analyze Assignment Load
1
AOL
2
API
12
Approval from email notification
2
Approve Time
7
Approved Budget User Data Fields
1
Assignment update using position update ...
2
Attachment with notification
2
Audit Logs
7
Audit Trail
5
Authentication
5
Autofill
2
background service restart
1
Bar chart
4
Certification
6
Change Project Name
1
CHPERPDBA@mountsinai.org
1
Clear cache issue wrt RequestRulesUserLibrary...
1
Closed Project
3
Confirmation
9
Copy_Header's_User_Data_Default_No
2
cost health icon
1
Dashboard Usability
13
Dashboards
19
Databases
7
decimals
4
Demand Management
34
department
1
deployment
8
Display info on logon page
1
Enabling Floating License
1
Export to PDF
7
exporting to PDF and Excel
7
Feature Request
68
Field Type
7
file attachment
4
Filters
10
Financial & Staffing Profile
17
Financial Summary
27
FinancialSummaryAPI
2
Github
1
Global KPI
3
Import from excel to Table component
3
in-line editing
2
Include use
11
Idea ID: 2857582

Allow specific users/security groups to reopen a request after closure

puthar
Status: Waiting for Votes

Waiting for Votes

See status update history

Hi,

We have a requirement to allow only specific users or security groups to have access to the reopen option  in a project. This is currently not possible.

When a reopen step for the request has been defined, any user with "Edit Request" access grant and access to the request will be able to reopen it.

Please can you provide an solution to allow specific users or security groups the capability to reopen a request?

Regards,

Alfred Puth

Regards,

Alfred Puth

iOCO: Senior PPM Consultant

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.