[jbosstools-issues] [JBoss JIRA] (JBIDE-21650) Make Import OS3 Application more context-oriented

[Viacheslav Kabanovich (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-21650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13158945#comment-13158945 ] 

Viacheslav Kabanovich commented on JBIDE-21650:
-----------------------------------------------

[~mlabuda], is not fixing JBIDE-21617 addressed that problem? Could you please verify that what [~fbricon] did (copied from his comment):
1. Only display BuildConfig selection when necessary.
2. Only display relevant BuildConfigs when selecting a project
works, and if there are use cases not covered by that fix, please describe them in this issue.



> Make Import OS3 Application more context-oriented
> -------------------------------------------------
>
>                 Key: JBIDE-21650
>                 URL: https://issues.jboss.org/browse/JBIDE-21650
>             Project: Tools (JBoss Tools)
>          Issue Type: Enhancement
>          Components: openshift
>    Affects Versions: 4.3.1.Beta2
>            Reporter: Marián Labuda
>              Labels: import_wizard, openshift_v3
>
> Currently we don't make difference from where Import Application... context menu item in OpenShift Explorer view is invoked. If a connection contains 2 and more projects, and at least 2 of those projects contains a build config, there are always listed all projects with build configs in Import OpenShift Application wizard no matter what. Even if I have selected a specific service or project, invoked Import Application wizard lists all projects and build configs. It would be nice to have it more context oriented - when select Import Application... context menu item on a specific service, build config related to this service should be preselected in wizard (maybe only project where the service is located should be listed and its build configs with selected the selected one). If opened via context menu of a project, project should be preselected (maybe only project with its build config could be visible).



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)