Project

General

Profile

Bug #4007

Append jail counter >0 to plugin name in configuration tree

Added by Marc - over 6 years ago. Updated about 3 years ago.

Status:
Closed: Not To Be Fixed
Priority:
No priority
Assignee:
John Hixson
Category:
GUI (new)
Target version:
Severity:
New
Reason for Closing:
Reason for Blocked:
Needs QA:
Yes
Needs Doc:
Yes
Needs Merging:
Yes
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

Currently it's not so obviously identifiable to which jail a plugin is related to.

same_plugins.png (2.69 KB) same_plugins.png Marc -, 01/25/2014 12:11 AM
356

History

#1 Updated by Jordan Hubbard over 6 years ago

  • Assignee set to John Hixson
  • Target version set to 72

Seems a sensible request. Screening to next update.

#2 Updated by John Hixson over 6 years ago

  • Status changed from Unscreened to Screened

I agree with this. I don't like being unable to distinguish which plugins belong to which jail. However, I don't think a counter is the right way to do. Have any better ideas? Perhaps have the plugin name listed with the jail name in []'s? eg: Bacula Storage [jail1], Bacula Storage [jail2], etc?

#3 Updated by Marc - over 6 years ago

The idea for the counter raises up, because that's the way it is currently done to disambiguate jails (e.g., bacula-sd_<n>).

To me something like [jail<n>] would provide a too small gain of information compared to the additional (static) characters.

Using the jail's name sounds reasonable. It has the potential to result in quite large labels though.
Since I've not found a specification or issue about the obviously upcoming refactoring of the WebUI ("death to bla"), someone should take into consideration that this would comply with the new UI.

#4 Updated by John Hixson over 6 years ago

Marc - wrote:

The idea for the counter raises up, because that's the way it is currently done to disambiguate jails (e.g., bacula-sd_<n>).

To me something like [jail<n>] would provide a too small gain of information compared to the additional (static) characters.

Using the jail's name sounds reasonable. It has the potential to result in quite large labels though.
Since I've not found a specification or issue about the obviously upcoming refactoring of the WebUI ("death to bla"), someone should take into consideration that this would comply with the new UI.

Well, the plugin jails e themselves use a counter to increment the name, however, that is not what is displayed. I suppose we could take the number that the jailname is assigned use that for the "counter". I see several problems with that approach though. It may not necessarily be consistent, if you upload a plugin, it will get a name of "customplugin_N" where N is a number that can be the same as the the jail number. I've already modified the code to add the jailname to the tree menu name, and honestly I don't really like how it looks. I have not committed it as I would like more input on this. Still open to ideas ;-)

#5 Updated by Marc - over 6 years ago

Another idea I could think of is a kind of 'Visible Name' that has technically no usage but (when set) is used for representation in UI.

This is something I know from Zabbix.
Any host asset is technically and visually identified by a (correct) hostname. Optionally one may set a 'Visible Name' as hostname replacement in the frontend.

Pro: anybody can handle this issue as one sees fit.
Con: No automatism

#6 Updated by John Hixson over 6 years ago

  • Status changed from Screened to Closed: Not To Be Fixed
  • Target version changed from 72 to 49

I still can't come up with a clean way of doing this. Until a method of doing so that "makes sense" is brought up, I'm throwing this ticket out ;-) If a sane way of doing so is decided on , then feel free to bring it up and re-open the ticket ;-)

#7 Avatar?id=14398&size=24x24 Updated by Kris Moore about 3 years ago

  • Target version changed from 49 to N/A

Also available in: Atom PDF