Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UI: Latest version does not allow for drag and drop reordering of service dialog elements #1229

Closed
Cameronwyatt opened this issue Dec 12, 2014 · 6 comments
Assignees
Labels

Comments

@Cameronwyatt
Copy link

This is present in CloudForms 3.1, but should also be present in the latest version of ManageIQ.

When creating/editing service dialogs in CloudForms 3.0, you could drag and drop elements to change their positioning. This no longer works in CloudForms 3.1. The drag and drop will happen in the UI, but the "save" button is greyed out. Even if you go into the developer console and change it so that the "save" button is active, saving doesn't actually change the position of the element.

@Fryguy
Copy link
Member

Fryguy commented Dec 12, 2014

@dclarizio Please take a look.

@Fryguy Fryguy added the bug label Dec 12, 2014
@dclarizio
Copy link

Hey Cameron,

We took a look at the master branch on ManageIQ and do not see this issue, tho we did have an issue with a recent change that didn't enable the Save button, which was then fixed.

We also tested on the latest Cloudforms branch and do not see the issue there either.

Do you have a system we can access that displays this behavior? Let me know.

Thanks,
Dan

@Cameronwyatt
Copy link
Author

Hi @dclarizio, thanks for looking into this. I guess that we don't have the latest changes pulled in as I thought. Could you link me to the issue that you mentioned? Maybe I can pull in just the code to fix that.

@h-kataria
Copy link
Contributor

Cameron,
Issue with Save/Reset buttons in Dialog editor for was fixed by #1077 PR. Let us know if this doesn't resolve the issue in your environment.
Thanks,
Harpreet.

@chessbyte
Copy link
Member

@dclarizio Suggest closing this issue since you cannot reproduce it on master. If @Cameronwyatt can reproduce the issue, then he should re-open it with details.

@Cameronwyatt
Copy link
Author

@dclarizio @chessbyte closing. An update fixed this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants