Network/Router forms show readonly ID/name fields

Bug #1671593 reported by Akihiro Motoki
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Dashboard (Horizon)
Fix Released
Low
Akihiro Motoki

Bug Description

In horizon design we don't show IDs as they are not user friendly, but forms in the network and router panels show ID as read-only fields. As the author of these panels, there is no special reason other than the lack of Django knowledge and they are used to retrieve IDs of target resource or parent resource.

In addition, we don't usually show resource name of parent resource, but port create form does.

These inconsistency is better to be fixed.

Tags: neutron
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to horizon (master)

Fix proposed to branch: master
Review: https://review.openstack.org/443928

Changed in horizon:
status: New → In Progress
Changed in horizon:
milestone: pike-1 → pike-2
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to horizon (master)

Reviewed: https://review.openstack.org/443928
Committed: https://git.openstack.org/cgit/openstack/horizon/commit/?id=cb391cc933f49a2756354c78faaf2819f13cdd8d
Submitter: Jenkins
Branch: master

commit cb391cc933f49a2756354c78faaf2819f13cdd8d
Author: Akihiro Motoki <email address hidden>
Date: Thu Mar 9 18:08:23 2017 +0000

    Do not display UUID in network/rotuer forms

    In horizon design we don't show IDs as they are not user friendly,
    but forms in the network and router panels show ID as read-only fields.
    These fields are only used to retrieve ID of target or parent resource,
    but they can be retrieved from "self.initial". (Note that 'initial'
    data is set from url parameters in the django views.)

    We don't usually show resource name of parent resource as well.
    Let's do it consistently for network/router forms.

    Change-Id: Ibd4c594e79889e8c605203a79bc35e1ffaa40703
    Closes-Bug: #1671593

Changed in horizon:
status: In Progress → Fix Released
Changed in horizon:
milestone: pike-2 → pike-3
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/horizon 12.0.0.0b3

This issue was fixed in the openstack/horizon 12.0.0.0b3 development milestone.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.