Skip to content
This repository has been archived by the owner on Jul 21, 2023. It is now read-only.

Remove migration plans from Service Catalog Items #435

Closed
bthurber opened this issue Jun 22, 2018 · 5 comments
Closed

Remove migration plans from Service Catalog Items #435

bthurber opened this issue Jun 22, 2018 · 5 comments
Labels
bz Issues filed by QE or having a BZ stale
Projects

Comments

@bthurber
Copy link

Description of problem:
When creating migration plans in the Migration plugin, they also appear under Services > Catalogs > Catalog Items.

Version-Release number of selected component (if applicable):
5.9.3 and latest MiQ nightly

How reproducible:
Everytime

Steps to Reproduce:

  1. In Migration plugin, create a migration plan
  2. Navigate to Services > Catalogs > Catalog Items
  3. Migration plans are listed

Actual results:
Migration plans are listed under: Services > Catalogs > Catalog Items

Expected results:
Migration plans do not appear in the Service Catalog

@AllenBW AllenBW added this to Backlog in v2v UI Jun 26, 2018
@priley86
Copy link
Member

is this a backend issue? Or do we need to specify some additional attribute? Forgot to ask about this yesterday...

@AllenBW
Copy link
Member

AllenBW commented Jun 28, 2018

@ManageIQ/core hi friends 👋 yer friendly neighborhood v2v ui team needs help here pretty please

@gmcculloug
Copy link
Member

This is being tracked here: https://bugzilla.redhat.com/show_bug.cgi?id=1594408

I have talked to @dclarizio about it yesterday and I think we just need to filter out the Migration plans when requesting the list of Service Template objects. This is the first Service Template sub-class that we want to remove.

Waiting for @h-kataria to return from PTO next week so we can address.

@AllenBW
Copy link
Member

AllenBW commented Jun 28, 2018

Thanks for the update on this @gmcculloug 🙇‍♀️ 🍭 🤗

@priley86 priley86 added the bz Issues filed by QE or having a BZ label Jul 10, 2018
@miq-bot
Copy link
Member

miq-bot commented Jan 14, 2019

This issue has been automatically marked as stale because it has not been updated for at least 6 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.

Thank you for all your contributions!

@miq-bot miq-bot added the stale label Jan 14, 2019
v2v UI automation moved this from Backlog to Done May 16, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bz Issues filed by QE or having a BZ stale
Projects
v2v UI
  
Done
Development

No branches or pull requests

6 participants