Current set up to deploy content is confusing for some users - we should make it easier.
Users would like to deploy their files direct to a Deployment Repository or Content Repository with an option to distribute it to the desired server-groups without duplicated menus (like duplicated ServerGroups and DomainDeployments in host and domain controllers). Also, users would like an easy way to find which ServerGroups the file was deployed by showing it when clicking in the deployment file.
The EAP 6 names should be kept, like Manage Deployments, Content Repository, Available Deployment Content, and others.
*** Bug 1100247 has been marked as a duplicate of this bug. ***
merged to master in d3c6251b5f8aebf1ad4c24b703e3f1adffe338eb
Heiko Rupp <firstname.lastname@example.org> updated the status of jira JON3-25 to Resolved
I now can manage Server Group assignment for deployments. Does it make sense to give users the ability to add/upload new war/ear directly from DomainDeployments? It's counterintuitive to only be able to manage group assignment here and have to go to another place to upload my war/ear. See attachment.
Created attachment 901907 [details]
Moving to ON_QA as available to test with brew build of DR01: https://brewweb.devel.redhat.com//buildinfo?buildID=373993
mfoley user <email@example.com> updated the status of jira JON3-25 to Reopened
mfoley user <firstname.lastname@example.org> updated the status of jira JON3-25 to Resolved
marking as verified - jira is resolved, no blocking issues