Feature Overview (aka. Goal Summary)

An elevator pitch (value statement) that describes the Feature in a clear,
concise way.

From RHDHPLAN-876, it was pointed out that RHDH shouldn't let users attempt to modify roles that are defined in source. Today, RHDH is happy to let users try, and only at that point, return an error that it isn't possible. This error comes far too late in the process and results in a confusing and poor user experience that RHDH should improve if possible.

The flow they experienced, along with pictures, is documented here.

Goals (aka. expected user outcomes)

The observable functionality that the user now has as a result of receiving
this feature. Include the anticipated primary user type/persona and which
existing features, if any, will be expanded.

Understand if we have a mechanism that the UI can determine if roles come from source and can't be directly edited, or are mutable, and can be edited within RHDH. If the solution is simple enough, consider making UI improvements now, or create a follow up feature that we can plan for a future release.

Requirements (aka. Acceptance Criteria):

A list of specific needs or objectives that a feature must deliver in order
to be considered complete. If the feature spans across releases then good
to have scope for each release with acceptance criteria. Be sure to
include nonfunctional requirements such as security, reliability,
performance, maintainability, scalability, usability, etc.

• Perform a spike to see what, if any, API or other mechanisms we might have that we could utilize for the UI to identify source controlled roles.
• Create a followup feature if necessary for future planning that details our options

Out of Scope (Optional)

High-level list of items that are out of scope.

Complex changes would be handled via a follow up feature.

Customer Considerations (Optional)

Provide any additional customer-specific considerations that must be made
when designing and delivering the Feature. Initial completion during
Refinement status.

<your text here>

Documentation Considerations

Provide information that needs to be considered and planned so that
documentation will meet customer needs. If the feature extends existing
functionality, provide a link to its current documentation.

<your text here>