search

Icinga / icinga-web

Icinga Web 1.x, the old new web interface (EOL 31.12.2018)
22 stars 11 forks source link

[dev.icinga.com #2968] New Expand feature not work properly (current gitmaster 31ef...) #862

Closed icinga-migration closed 12 years ago

icinga-migration commented 12 years ago

This issue has been migrated from Redmine: https://dev.icinga.com/issues/2968

Created by ossmon on 2012-08-08 11:50:38 +00:00

Assignee: (none) Status: Closed (closed on 2012-10-11 22:06:30 +00:00) Target Version: (none) Last Update: 2012-10-11 22:06:30 +00:00 (in Redmine)

Icinga Version: 1.7.0
Icinga Web Version: 1.8.0
IDO Version: 1.7.0
OS Version: REHL6.1
DB Type: MySQL
DB Version: UNKNOWN
Browser Version: UNKNOWN

The new icinga-web version 1.7.2 introduce a redesign.of some columns links. For example in the service status grid, the columns info, history and host was deleted and they are now reachable with an expand line (there is now an expand link in front of the line)

The problems is:

1) a click on the expand link show the expand information (and the whole line is selected/checked) but when you release the mouse, the expand information disappear.

2) not only the expand link display the expand information but also a click on the line or a click on a pnp/ingraph icon. There is a conflict with other active links.

Solution: only the expand link should activate/deactivate the expand information and shouldn't check the line

icinga-migration commented 12 years ago

Updated by tgelf on 2012-08-08 12:26:03 +00:00

Hi ossmon,

the feature you describe is to be found in the current master and may be available in 1.8. Version 1.7.2 has been released yesterday and shall not show this effect.

Regards, Thomas Gelf

icinga-migration commented 12 years ago

Updated by ossmon on 2012-08-08 12:40:22 +00:00

Hi Thomas, i have downloaded the actual git master (31ef...) today morning and i have this effect. Is it not the version 1.7.2 ?

icinga-migration commented 12 years ago

Updated by tgelf on 2012-08-08 14:30:13 +00:00

No. The master is where active development is going on, things there are broken very often. You can download 1.7.2 from Sourceforce:

http://sourceforge.net/projects/icinga/files/icinga-web/1.7.2/icinga-web-1.7.2.tar.gz/download

Each stable release has it's own branch for bugfixes, so if 1.7.2 would have a known bug and you are looking for a fix that's where you can usually find fixed releases without new (and often uncomplete) features. Currently this is r1.7, to be found is here:

https://git.icinga.org/?p=icinga-web.git;a=shortlog;h=refs/heads/r1.7

You can find a list of all branches here (scroll down): https://git.icinga.org/?p=icinga-web.git;a=summary

Cheers, Thomas

icinga-migration commented 12 years ago

Updated by ossmon on 2012-08-08 15:34:06 +00:00

Ok, it was for me not really clear which differences exist between master and a branch. now it is clear. you can close the issue or it can help also the developer of the new feature. i've installed in my test-environment now the version 1.7.2 and the new feature is no more present.

One more question: because i'am always interested to test new feature and for this i download the git master, what should i do when i find a problem in the git master version ? nothing or create an issue ?

icinga-migration commented 12 years ago

Updated by tgelf on 2012-08-08 16:02:12 +00:00

An issue is IMHO always helpful. Mentioning that you are using the current master as you want to assist developers sometimes prevents you from getting a harsh rant in such cases ;-)

icinga-migration commented 12 years ago

Updated by mfriedrich on 2012-08-08 21:15:34 +00:00

if you encounter an issue with git installs, please always include

other than that, the normal procedure for issues (possible important config, logs, screenshots, etc)

icinga-migration commented 12 years ago

Updated by ossmon on 2012-08-09 05:57:27 +00:00

Hi dnsmichi, i don't have a git because git ports are blocked at work. I download always the tar.gz over http. But i can give the branch info (as in the title in this issue)

Better would be to enter the branch version in the new mandatory version fields. But as i created this issue, i tried to enter 'git master' in the field 'Icinga Web Version' but it was not accepted.

Which syntax is allowed for the new 4 version fields ?

icinga-migration commented 12 years ago

Updated by mhein on 2012-08-23 09:43:36 +00:00

Hi.

The master introduces the upcomming releases which is at present 1.8.0. The syntax for the version field is 0.0.0

Kind regards, Marius.

icinga-migration commented 12 years ago

Updated by jmosshammer on 2012-09-30 11:48:22 +00:00

Does this stil occur?

icinga-migration commented 12 years ago

Updated by ossmon on 2012-10-01 05:57:04 +00:00

The two problems described in the issue don't occur anymore in the git master (b607... from 26.09.12).

But another small problem exist:

=> One click too much to hide the expand line, i think.

icinga-migration commented 12 years ago

Updated by mfriedrich on 2012-10-11 22:06:30 +00:00

i guess that's more of a get-used-to it thingy, than a real bug.