Description of problem: Unable to add Long Description for Playbook based Catalog Items Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. look at the service catalog, there's a line that says "long description" 2. go to the catalog item and try to edit it 3. Actual results: salty tears Expected results: a way to edit it. Additional info: This happened with orchestration based catalog items not too long ago, the fix is probably similar.
Please assess the impact of this issue and update the severity accordingly. Please refer to https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity for a reminder on each severity's definition. If it's something like a tracker bug where it doesn't matter, please set it to Low/Low.
We have the same problem at customer, it would be nice to be able to set the long description for ansible jobs, instead of only being able to do it for all other kinds of jobs. I can see this is from august 2018, can we get some kind of traction on it ?
https://github.com/ManageIQ/manageiq-ui-classic/pull/4402
New commit detected on ManageIQ/manageiq-ui-classic/master: https://github.com/ManageIQ/manageiq-ui-classic/commit/460e6d8fc16905f3d743047991de4fde321d6721 commit 460e6d8fc16905f3d743047991de4fde321d6721 Author: Richard Vsiansky <r.vsia> AuthorDate: Thu Aug 2 07:18:56 2018 -0400 Commit: Richard Vsiansky <r.vsia> CommitDate: Thu Aug 2 07:18:56 2018 -0400 Add long_description field using codemirror editor in Ansible Playbook fixes https://bugzilla.redhat.com/show_bug.cgi?id=1482905 app/views/catalog/_st_angular_form.html.haml | 113 +- 1 file changed, 62 insertions(+), 51 deletions(-)
Verification blocked by https://bugzilla.redhat.com/show_bug.cgi?id=1655745
Verified in Version 5.10.0.32.20190115185124_c957ada
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2019:0212