[overlord-issues] [JBoss JIRA] (ARTIF-645) Allow users to supply extensions through a new plugin architecture

[ https://issues.jboss.org/browse/ARTIF-645?page=com.atlassian.jira.plugin.... ] Gary Brown commented on ARTIF-645: ---------------------------------- Like the idea of a pluggable architecture - especially in respect of the UI. The current UI is very much a generic browser to navigate around a wide range of artifacts and view their metadata and relationships. However the information held within the repository could be idea for business specific views - so this pluggable approach could be one way in which organisations could define their build specific views, presenting the key information they are interested in, and allowing users to navigate through the relevant subsets of information they are interested in. For example, one usecase I heard related to the deployment lifecycle information being stored in SRAMP, was having service reports that showed how long it took to progress though the various stages of the lifecycle, and who (i.e. which teams) delayed the deployment. Although with custom views, it may also be good to look at this capability in the context of fine grained access control, to potential enable only some of these custom views to be offered/presented to specific users - e.g. a business user may not be presented with the generic browser and instead may only see a specific set of the custom views, to restrict (a) the information they see (presented at a suitable high level) and (b) the way in which they can navigate around the model. -- This message was sent by Atlassian JIRA (v6.3.11#6341)