Ticket #2279 (closed defect: Fixed)

Opened 13 months ago

Last modified 8 weeks ago

ZenPack Export menu item should be in page menu

Reported by: jstevens Owned by: jstevens
Priority: 2 - High Milestone: zenoss-2.2
Component: ZenPack Version: 2.1.0
Keywords: zenoss-2.1.1-patched Cc:
Community Patch Attached: Deployed @ Customer:
Installer: Maintenance Target:
Specific ZenPack: Maintenance Status:
Documentation Note?: Not required Regression:

Description

The Export menu item is in the table menu for the zenpack objects. This didn't make much difference when there was only one table on the page. Now there are two and the Export menu item looks like it applies only to the zenpack objects, not the zenpack itself. The menu item needs to be in the page menu.

Change History

Changed 13 months ago by jstevens

(In [7370]) refs #2279

  • Moved Export ZenPack menu item to page menu

This is complete, but not yet approved to be moved into branch.

Changed 13 months ago by jstevens

  • keywords zenoss-2.1.1-proposed added; zenoss-2.1.1 removed
  • status changed from new to closed
  • resolution set to fixed

Changed 13 months ago by jstevens

Approved for 2.1.1 but migrate script not review yet

Changed 13 months ago by jstevens

  • keywords zenoss-2.1.1-accepted added; zenoss-2.1.1-proposed removed

Changed 13 months ago by jstevens

(In [7474]) refs #2279

Changed 13 months ago by marc

(In [7477]) Patching r7370 to 2.1.x branch

Changed 13 months ago by marc

(In [7478]) Patching r7474 to 2.1.x branch

Changed 13 months ago by marc

  • keywords zenoss-2.1.1-patched added; zenoss-2.1.1-accepted removed

Changed 12 months ago by jstevens

  • status changed from closed to reopened
  • resolution fixed deleted

Migrate script works, but change is not in a clean install of trunk, even after a zenmigrate.

Changed 12 months ago by jstevens

I suspect this is not showing in trunk because script is set to version 2.1.1 and we are currently on 2.2. Manually running that specific migrate script will probably fix it. Did we do something wrong with the numbering of the db for this migrate script or is this a systemic issue with migrate scripts that are patched to branches?

Changed 11 months ago by jstevens

  • status changed from reopened to closed
  • resolution set to fixed

I think I was simply wrong about the not being in trunk thing. It appears fine in my latest install.

Changed 8 weeks ago by bbibeault

  • documentation set to Not required
  • reviewed set to 1
Note: See TracTickets for help on using tickets.